# CVE-2026-101723: Vulnerability in the Oracle Agile PLM MCAD Connector product of Oracle Supply Chain (component: CAX Client).


- **Severity:** Medium 6.7 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** GHSA-xvgh-qpm4-j93c

## What is CVE-2026-101723?

CVE-2026-101723 is a medium-severity vulnerability in Oracle Agile PLM MCAD Connector, published on 20 Oct 2026. 

### Official description

Vulnerability in the Oracle Agile PLM MCAD Connector product of Oracle Supply Chain (component: CAX Client).   The supported version that is affected is 3.6. Difficult to exploit vulnerability allows low privileged attacker with logon to the infrastructure where Oracle Agile PLM MCAD Connector executes to compromise Oracle Agile PLM MCAD Connector.  Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of Oracle Agile PLM MCAD Connector. CVSS 3.1 Base Score 6.7 (Confidentiality, Integrity and Availability impacts).  CVSS Vector: (CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H).

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-101723?


## How do I fix CVE-2026-101723?

No fix has been published for CVE-2026-101723 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-101723 being exploited?

There is no known exploitation of CVE-2026-101723 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-101723 and fix it if it is affected.

What it is: CVE-2026-101723 is a medium-severity vulnerability in Oracle Agile PLM MCAD Connector, published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-101723 in the wild and no public exploit code.

Affected product: Oracle Agile PLM MCAD Connector. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-101723/ (Markdown: https://insights.sbomify.com/CVE-2026-101723/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-101723
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-101723
- OSV: https://osv.dev/vulnerability/CVE-2026-101723

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-101723/
Summaries are generated and may contain mistakes; the official description above is the record.