On this page (7 sections)
A critical vulnerability, CVE-2026-127369, affects the Reconciliation Manage component of Oracle Hyperion Financial Close Management. According to the NVD record, an unauthenticated attacker with network access via Oracle Net can compromise the product and read or modify its data. The record was published on 2026-11-17 with a CVSS 3.1 base score of 9.1.
A second record published the same day, CVE-2026-127362, describes the same product, component, version and score, but reachable over HTTP instead of Oracle Net. Anyone running Hyperion Financial Close Management, or hosting it for a finance team, should treat both as one patching task.
What was published
Both records describe a vulnerability in the Reconciliation Manage component of Oracle Hyperion Financial Close Management, a finance product. The records call the flaw easily exploitable, needing no login and no user interaction. Both NVD entries point to the same reference, Oracle's security alert page, which is where patch details should be confirmed.
At the time of writing, the only sources available are the two NVD entries. There is no independent analysis, no proof-of-concept reporting and no statement about exploitation in the wild. Treat any claim beyond the records as unconfirmed.
Technical details
The records give a limited technical picture. The CVSS vector for both is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. In plain terms:
- AV:N - reachable over the network, no local access required.
- AC:L and PR:N - low complexity and no privileges needed, so no account is required.
- UI:N - no user has to click or approve anything.
- C:H and I:H - high impact on confidentiality and integrity: an attacker could read all data the product can access and create, change or delete critical data.
- A:N - no availability impact is listed, so this is about data theft and tampering rather than crashing the service.
The two CVEs differ only in the access path. CVE-2026-127369 is exploitable via Oracle Net, while CVE-2026-127362 is exploitable via HTTP. The records do not name a weakness class (no CWE is listed), and they do not explain the root cause. We will not guess at one.
Who is affected
The records list one affected supported version: 11.2.26.0.000. Organizations running that version of Hyperion Financial Close Management are in scope. The research does not say whether other versions are affected or unaffected, so check Oracle's advisory rather than assuming a different version is safe.
Exposure depends heavily on network placement. Financial systems like this are often internal, but a flaw that needs no authentication makes reachability the main question. Risk is highest where the Oracle Net listener or the HTTP interface can be reached from the internet, a partner network, a flat internal network or a compromised workstation.
How to check your exposure
Start with inventory and reachability. You need to know whether you run the affected version and who can connect to it.
- Find every Hyperion Financial Close Management instance, including test and disaster-recovery copies, and record its exact version. Compare against 11.2.26.0.000.
- Open Oracle's security alert page and look up the Hyperion Financial Close Management entry for these two CVE identifiers and the patch instructions.
- List which networks can reach the application's HTTP port and its Oracle Net listener. Ask your network or hosting team for firewall rules and security group settings if you do not own them.
- Review application, web server and listener logs for connections from unexpected addresses, especially unauthenticated requests or connections outside business hours.
If you are unsure what your public footprint looks like, a read-only external check such as Webforta Scan can help show what is visible from the internet on sites you control. It cannot tell you whether an internal Hyperion server is patched.
What to do now
- Confirm whether you run Hyperion Financial Close Management 11.2.26.0.000, on every environment.
- Read Oracle's advisory and apply the patch or workaround it provides for CVE-2026-127369 and CVE-2026-127362. Apply both together.
- Until patched, restrict network access: block the HTTP interface and Oracle Net listener from the internet and from any network that does not need them.
- Limit access to a short allow list of application servers, finance user networks and administration hosts.
- Review logs and database audit records for unusual reads, changes or deletions since the 2026-11-17 publication, and earlier if your retention allows.
- If you find suspicious activity, preserve logs, involve your incident response contact and verify the integrity of critical financial records against backups or source systems.
- Record the patch date and version in your change log so auditors and finance owners can see the issue was closed.
Detection and monitoring afterwards
Because the flaw needs no credentials, the logs may not show a failed login before suspicious activity. Focus on access patterns instead: new source addresses reaching the application or listener, spikes in data reads, and unexplained changes to records.
- Alert on new or unexpected clients connecting to the Oracle Net listener and the HTTP interface.
- Watch for bulk exports or unusual query volume against financial close data.
- Keep database and application audit logging enabled and sent to a system the application server cannot modify.
- Subscribe to Oracle's security alerts so the next issue does not depend on a news article.
For public-facing parts of your estate, certificate, DNS and header-change monitoring helps you notice unplanned changes, though it does not replace patching or network controls on internal finance systems.
What we do not know yet
The NVD records do not state the fixed version or patch identifier, a root cause, or whether the flaw is being exploited. No exploit has been reported in the research we reviewed, and only one independent publisher covers the story so far. We will not fill those gaps with assumptions. Check Oracle's advisory for authoritative remediation details and re-check it as Oracle updates it.
For general patching and exposure habits, the small business website security guide is a useful reference, and our security news archive tracks new advisories as they appear.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
