# CVE-2026-87413: Vulnerability in the Oracle Solaris product of Oracle Systems (component: Filesystems).


- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 21 Oct 2026
- **Also known as:** GHSA-vqhq-jh64-6g2g

## What is CVE-2026-87413?

CVE-2026-87413 is a medium-severity vulnerability in Oracle Solaris, published on 20 Oct 2026. 

### Official description

Vulnerability in the Oracle Solaris product of Oracle Systems (component: Filesystems).   The supported version that is affected is 11.4. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle Solaris executes to compromise Oracle Solaris.  Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle Solaris. CVSS 3.1 Base Score 5.5 (Availability impacts).  CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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


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

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

## Is CVE-2026-87413 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected product: Oracle Solaris. 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-87413/ (Markdown: https://insights.sbomify.com/CVE-2026-87413/index.md)
```

## Sources

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

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