OSV-2026-717 Stack-use-after-scope in enter_block_callback
Not scored
Published
Check this codebase for OSV-2026-717 and fix it if it is affected.
What it is: OSV-2026-717 is an use after free vulnerability in md4c, published on 12 May 2026.
Exploitation: There is no known exploitation of OSV-2026-717 in the wild and no public exploit code.
Affected packages and fixed versions:
- md4c (OSS-Fuzz): affected all versions; no fix listed
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/OSV-2026-717/ (Markdown: https://insights.sbomify.com/OSV-2026-717/index.md)
A stack-use-after-scope vulnerability in the markdown parser allows attackers to cause a denial of service via crafted input.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2026-717?
OSV-2026-717 is an use after free vulnerability in md4c, published on 12 May 2026.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=511831392
Crash type: Stack-use-after-scope READ 4
Crash state:
enter_block_callback
md_process_all_blocks
md_parse
Which versions are affected by OSV-2026-717?
1 open source package ship an affected version, including md4c.
| Package | Affected | Fixed in |
|---|---|---|
md4c OSS-Fuzz | All versions | None |
How do I fix OSV-2026-717?
No fix has been published for OSV-2026-717 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.
Is OSV-2026-717 being exploited?
There is no known exploitation of OSV-2026-717 in the wild and no public exploit code.