On this page (8 sections)
On 2026-11-17, NVD published CVE-2026-127327, a critical vulnerability in the Security component of Oracle AutoVue, part of Oracle Supply Chain. According to the NVD entry, an unauthenticated attacker with network access over HTTP can compromise the product, and a successful attack can result in takeover of Oracle AutoVue.
Three sibling records, CVE-2026-127326, CVE-2026-127325 and CVE-2026-127324, were published the same day with the same description and score. If your organization runs AutoVue 21.1.0, especially anywhere reachable over HTTP from outside, treat this as urgent.
What was published
The record describes an easily exploitable flaw in the Security component of Oracle AutoVue. The affected supported version is 21.1.0. The CVSS vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, which translates to: reachable over the network, low attack complexity, no privileges, no user interaction, unchanged scope, and high impact on confidentiality, integrity and availability.
The records point to an Oracle security alert page, cspunov2026, as their reference. The research available for this article does not include the content of that page, so this article cannot confirm a fixed version, patch name or workaround. Read the Oracle alert directly for that.
Four CVEs, one description
All four records carry identical text and the same 9.8 score. Only CVE-2026-127325 lists a weakness type: CWE-306, Missing Authentication for Critical Function. The other three list no CWE. It is not confirmed whether the four are distinct flaws in different code paths or entries for related issues, and the records do not say. Do not assume that addressing one of them covers the others until Oracle's alert says so.
What the weakness class means
CWE-306 describes a function that should require authentication but does not. In practice, that means a request sent over HTTP could reach sensitive functionality without logging in. A flaw that needs no credentials and no user click is the kind attackers can scan for at scale once details become widely known.
Remember that the CWE-306 label is attached to only one of the four records. It is reasonable to suspect missing authentication is involved in the others, but the research does not confirm it.
Who is realistically exposed
- Organizations running Oracle AutoVue 21.1.0, the only affected version named in the records.
- Any deployment where the AutoVue HTTP service can be reached from the internet, a partner network, or a flat internal network where many users and devices can connect.
- Teams that do not know whether AutoVue is still installed anywhere. An instance missing from your inventory cannot be patched.
Exploitation status is not stated in the research. No public exploit or in-the-wild attack is confirmed here, and the records show no CISA KEV entry. That can change quickly for a 9.8 unauthenticated flaw, so do not treat the lack of confirmed attacks as a reason to wait.
How to check your exposure
Start by finding out whether you run AutoVue and which version. Check your software inventory, Oracle licensing records, and the servers that may host it.
On a Linux host where you suspect AutoVue is installed, this read-only search lists paths with AutoVue in the name so you can find the install location and then check the version in the product's own documentation or admin console:
find / -maxdepth 4 -iname '*autovue*' -not -path '/proc/*' 2>/dev/nullNext, identify which network ports the AutoVue service listens on and who can reach them. This read-only command lists listening TCP sockets with their owning process on Linux; look for the AutoVue process and note which interfaces it is bound to:
ss -tlnpThen confirm from the network side. From a machine outside your trusted network, check whether the AutoVue HTTP port answers. If it does and you do not need that, restricting it is your first quick win.
What to do now
- Inventory every Oracle AutoVue instance and record the version. Anything on 21.1.0 is in scope.
- Open the Oracle security alert at https://www.oracle.com/security-alerts/cspunov2026.html and read the fix or patch instructions for AutoVue.
- Apply Oracle's patch or update as soon as your change process allows. Test where you can, but do not let testing delay a 9.8 fix for long.
- Until patched, restrict network access to the AutoVue HTTP service to the smallest set of hosts that need it, and remove any direct internet exposure.
- Put AutoVue behind a reverse proxy, VPN or authenticated gateway if remote users need it.
- Review web server, proxy and application logs since 2026-11-17 for unusual requests to AutoVue from unfamiliar addresses.
- If you see signs of compromise, isolate the host, preserve logs, and follow your incident response plan before patching over the evidence.
- Track all four CVE identifiers (127324 to 127327) in your vulnerability register so none is closed prematurely.
Detection and monitoring afterwards
A takeover of an application server can mean new accounts, changed configuration, new scheduled jobs or outbound connections the host never made before. After patching, keep watching for those signs, and check that the AutoVue host only talks to the systems it should.
On the web side, you can track changes with outside-in tooling. Webforta Monitor watches uptime, certificates, DNS and header changes, which helps you notice an unexpected change on a public hostname, and the free SSL checker shows what certificate a public endpoint presents. These do not detect or fix this specific flaw; patching and network restriction do that. For background on limiting exposure, see what is a WAF and small business website security.
What is still unknown
- Whether a fixed version or patch is available, and its identifier. The records reference an Oracle alert, but its content is not in our research.
- Whether the four CVEs are four separate flaws or overlapping entries.
- Whether anyone is exploiting these flaws. No exploitation is confirmed in the research.
- Which exact AutoVue endpoint or function is affected. The records do not say.
This article will need an update once Oracle's alert content and any exploitation reports are confirmed.
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.
- CVE-2026-127327: Vulnerability in the Oracle AutoVue product of Oracle Supply Chain (component: Security).
- CVE-2026-127326: Vulnerability in the Oracle AutoVue product of Oracle Supply Chain (component: Security).
- CVE-2026-127325: Vulnerability in the Oracle AutoVue product of Oracle Supply Chain (component: Security).
- CVE-2026-127324: Vulnerability in the Oracle AutoVue product of Oracle Supply Chain (component: Security).
