On this page (7 sections)
A critical vulnerability, CVE-2026-114881, was published on 2026-11-17 for the Document Management and Collaboration product of Oracle E-Business Suite (component: Attachments). According to the NVD record, it can be exploited by an unauthenticated attacker with network access over HTTP and carries a CVSS 3.1 base score of 9.1.
A second flaw in the same product and component, CVE-2026-114880, was published the same day with a higher score of 9.8. Anyone running Oracle E-Business Suite 12.2.x, especially with the application reachable from the internet, should treat both as one piece of work.
What was disclosed
The NVD description states that the flaw is easily exploitable and lets an unauthenticated attacker with network access via HTTP compromise Document Management and Collaboration. The listed impact is unauthorized access to critical data, or complete access to all data that the product can reach, plus the ability to cause a hang or a frequently repeatable crash, which NVD describes as a complete denial of service.
The scoring reflects that: high confidentiality impact, no integrity impact and high availability impact. In plain terms, the vector describes an attacker who can read data and knock the component offline, but the score does not claim they can change data.
The sibling flaw: CVE-2026-114880
The NVD record for CVE-2026-114880 describes the same product, component, version range and access conditions. The difference is the outcome: successful attacks can result in takeover of Document Management and Collaboration, with a CVSS 3.1 score of 9.8 and high impact on confidentiality, integrity and availability.
| CVE-2026-114881 | CVE-2026-114880 | |
|---|---|---|
| CVSS 3.1 base score | 9.1 | 9.8 |
| Vector | AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H | AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| Described impact | Access to critical data, complete denial of service | Takeover of the product |
| Affected versions | 12.2.3-12.2.15 | 12.2.3-12.2.15 |
| Published | 2026-11-17 | 2026-11-17 |
What we do not know yet
The research for this story is thin, and it is worth being clear about the gaps rather than guessing:
- No weakness class (CWE) is listed in the records, so the root cause is not stated.
- The records do not name a fixed version or patch number. Both point to an Oracle security alert page as the reference, and that page is where patch details should be confirmed.
- No source reports exploitation in the wild, and neither CVE shows a CISA Known Exploited Vulnerabilities entry in the data we have.
- Only the NVD records cover this so far, so there is no independent technical analysis yet.
Who is realistically exposed
Exposure depends on whether you run Oracle E-Business Suite 12.2 with Document Management and Collaboration in the 12.2.3-12.2.15 range, and whether HTTP access to it is possible from places an attacker can reach. If your deployment is reachable from the internet, your exposure is highest, because the flaw needs no login and no user interaction. Internal-only installations are still exposed to anyone who gets onto the internal network, such as through a compromised workstation or VPN account.
How to check your exposure
Start with an inventory rather than a scan. You need three answers: which release you run, whether the Attachments component of Document Management and Collaboration is in use, and which URLs of the application are reachable from outside.
- Confirm your E-Business Suite release and patch level in your own administration tooling and compare it with the 12.2.3-12.2.15 range.
- List every E-Business Suite web entry point and check, from an outside network, which ones answer over HTTP or HTTPS.
- Review web server and application logs for unusual requests to attachment-related paths, large response volumes, or repeated requests followed by service hangs or restarts.
- Note any unexplained slowdowns or crashes of the document management services since 2026-11-17, since the described availability impact is a repeatable hang or crash.
What to do now
- Open the Oracle security alert referenced by both CVE records and identify the patch or mitigation that applies to your 12.2.x release.
- Schedule the patch for both CVE-2026-114881 and CVE-2026-114880 together, prioritizing internet-facing environments first.
- Test in a non-production copy, then apply in production during a planned window.
- Until patched, restrict network access to E-Business Suite so that only required users and networks can reach it, for example through firewall rules or a reverse proxy allowlist.
- If you cannot patch quickly, consider whether the Document Management and Collaboration attachment functions can be limited to internal users.
- Rotate credentials and review stored documents for exposure if you find signs of suspicious access before patching.
Detection and monitoring afterwards
After patching, keep watching the application tier. Alert on spikes in requests to attachment endpoints, repeated 5xx errors, and unexpected restarts of the application services. Keep access logs long enough to look back at the days around 2026-11-17 if new details about exploitation emerge.
A web application firewall in front of the application can help limit who reaches it and add visibility, but it is a supplement to patching, not a replacement. See what a WAF is for what it can and cannot do. You can also use certificate and DNS monitoring to catch unexpected changes on the public hostnames that front your ERP systems, and browse the Webforta blog for other critical vulnerability write-ups to review in the same patch cycle.
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.
