# CVE-2026-86303: 92181 markdown md.c lds out-of-bounds

> Remote attackers can trigger an out-of-bounds read in the markdown library, potentially exposing memory or causing crashes.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-jvfg-5f69-7f59

## What is CVE-2026-86303?

CVE-2026-86303 is a medium-severity memory corruption vulnerability in 92181 markdown, published on 7 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was determined in 92181 markdown up to 058cab0cb7fb245a0ccc6b8446963ff8d573558f. Affected by this issue is the function lds of the file md.c. Executing a manipulation can lead to out-of-bounds read. The attack can be executed remotely. This product implements a rolling release for ongoing delivery, which means version information for affected or updated releases is unavailable. This patch is called c000d2f9cf390c315378d3717cf20911cf3e80a6. A patch should be applied to remediate this issue.

Weakness: CWE-125 (Out-of-bounds Read), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-86303 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86303 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86303 is a medium-severity memory corruption vulnerability in 92181 markdown, published on 7 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-86303 exists.

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

## Sources

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

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