On this page (8 sections)
CVE-2026-114863 is a critical vulnerability in the Oracle Universal Work Queue product of Oracle E-Business Suite, in the Media Integration component. According to the NVD record, an unauthenticated attacker with network access over HTTP can compromise the product, and a successful attack can result in takeover of Oracle Universal Work Queue.
If you run Oracle E-Business Suite 12.2.x, especially with the application reachable from the internet or from broad internal networks, this is worth checking today. The public record is short, so this article separates what is confirmed from what is still unknown.
What was published
The entry was published by the National Vulnerability Database on November 17, 2026 and added to the GitHub Advisory Database as GHSA-c2w7-7g2f-8g4f on November 18, 2026, where it is marked unreviewed. Both records list an Oracle page as a reference. The content of that page was not available to us, so we cannot say what patch details it contains. Check it directly.
The NVD entry repeats the same text as the GitHub advisory, so these are not two independent confirmations. At the time of writing we found no independent analysis, proof-of-concept report or incident write-up. Treat the details below as what the published record says, nothing more.
What the CVSS score tells you
The vector explains why the score is 9.8. Each element is taken from the published metrics:
| Metric | Value | Plain meaning |
|---|---|---|
| Attack vector | Network | Reachable remotely over HTTP, no local access needed |
| Attack complexity | Low | No special conditions to line up |
| Privileges required | None | No account or login needed |
| User interaction | None | No one has to click anything |
| Scope | Unchanged | Impact stays within the vulnerable component's security scope |
| Confidentiality / Integrity / Availability | High / High / High | Data exposure, modification and disruption are all possible |
In practice, a flaw with these metrics is the kind attackers tend to scan for at scale, because it needs no credentials and no victim action. That is general risk reasoning about the score, not a report of observed attacks.
What is not known
- The root cause. No CWE is assigned in the record, and no technical detail about the Media Integration weakness is public in our sources.
- The fixed version or patch identifier. The GitHub advisory lists patched versions as unknown, and the content of the referenced Oracle page was not available to us.
- Whether the flaw is being exploited. We found no confirmation either way.
- Whether any workaround exists. None is described in the sources.
Who is realistically exposed
The affected range is 12.2.3 through 12.2.15 of Oracle E-Business Suite, where Universal Work Queue is installed. Organizations that run EBS are the audience. Risk is highest where EBS web endpoints are published to the internet, or where internal networks are flat and widely reachable, because the flaw is described as exploitable over HTTP without authentication.
Versions outside 12.2.3-12.2.15 are not listed as affected, but the record only describes supported versions. If you run a release outside the listed range, confirm its status with Oracle rather than assuming it is safe.
How to check your exposure
Start by establishing your exact EBS release and whether Universal Work Queue is deployed. This read-only query, run in SQL*Plus or another client against the EBS database, should return the release name such as 12.2.x. It is a commonly documented query, but verify it against your Oracle documentation first:
SELECT release_name FROM fnd_product_groups;Then compare the result with the affected range 12.2.3-12.2.15 and check which patches your team has applied against the details on Oracle's referenced page. Also map which EBS URLs are reachable from the internet.
What to do now
- Confirm your EBS release and whether Oracle Universal Work Queue is installed.
- Open the Oracle page referenced by the record and look for the patch or guidance for CVE-2026-114863 and its prerequisites.
- Schedule the patch in a test environment first, then production, prioritizing internet-facing EBS tiers.
- Until patched, restrict network access to EBS web endpoints to the networks and partners that need them, for example through VPN, allow-lists or a reverse proxy.
- If a web application firewall sits in front of EBS, review its logging and rules, but do not treat it as a substitute for the patch. See what a WAF is for what it can and cannot do.
- Review web server and application logs for unusual unauthenticated requests to Media Integration or Universal Work Queue paths, and keep them for investigation.
- Take a verified backup before patching and record the pre-patch state so you can roll back if needed.
Detection and monitoring afterwards
Because the technical details are not public, you cannot rely on a known signature. Watch for behavior instead: new or unexpected administrative users in EBS, changes to work queue or media configuration you did not make, unexpected outbound connections from application servers, and spikes of unauthenticated HTTP requests from unfamiliar addresses.
For the public-facing side, an external scan of your hostnames can confirm what is actually reachable, and certificate and DNS monitoring can flag unexpected changes around your EBS entry points. Webforta Scan runs read-only checks on sites you verify and Webforta Monitor tracks uptime, certificates and DNS. Neither replaces applying Oracle's patch.
Timeline
| Date | Event |
|---|---|
| 2026-11-17 | CVE-2026-114863 published by the National Vulnerability Database |
| 2026-11-18 | Added to the GitHub Advisory Database as GHSA-c2w7-7g2f-8g4f (marked unreviewed) |
| 2026-11-18 | No exploitation or independent analysis found in the research for this article |
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.
