CVE-2026-6068

CRITICALNVD 9.69.6—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.6 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 64% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Elevated
9.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.6Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.6
EG Score
9.6(medium)
EG Risk
74(Attend)
EG Risk 74/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity96% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

April 10, 2026

Last Modified

May 26, 2026

Advisory Details (2)

Auto-updated Sep 14, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

CVE-2026-6068 – From Heap UAF to Persistent RCE in NASM | Project SEKAI

https://sekai.team/blog/nasm-cve-disclosure/cve-2026-6068
generic

NASM heap-use-after-free in -@ response file parsing via dangling depend_file · Issue #222 · netwide-assembler/nasm · GitHub

https://github.com/netwide-assembler/nasm/issues/222

Vendor Advisories for CVE-2026-6068(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
nasm2.15.05-1, 2.16.01-1, 2.16.01-1~hurd.1, 2.16.03-1, 3.01-1——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
nasm2.16.01-1, 2.16.03-1, 3.01-1——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
nasm2.16.03-1, 3.01-1——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
nasm2.16.03-1, 3.01-1——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 3× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 202 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-11 09:37 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 13:47 UTCEPSS rescore
  6. 2026-09-05 15:31 UTCEPSS rescore
  7. 2026-09-04 05:07 UTCEPSS rescore
  8. 2026-09-02 16:08 UTCOSV refresh
  9. 2026-09-02 14:12 UTCEPSS rescore
  10. 2026-09-01 13:54 UTCEPSS rescore
  11. 2026-09-01 04:40 UTCEPSS rescore
  12. 2026-08-30 19:17 UTCEPSS rescore
  13. 2026-08-30 01:22 UTCEPSS rescore
  14. 2026-08-28 21:42 UTCEPSS rescore
  15. 2026-08-26 14:47 UTCEPSS rescore
  16. 2026-08-25 13:49 UTCEPSS rescore
  17. 2026-08-23 00:19 UTCEPSS rescore
  18. 2026-08-21 23:49 UTCEPSS rescore
  19. 2026-08-20 22:56 UTCEPSS rescore
  20. 2026-08-19 17:04 UTCEPSS rescore
  21. 2026-08-18 13:49 UTCEPSS rescore
  22. 2026-08-18 13:49 UTCEPSS rescore
  23. 2026-08-17 13:47 UTCEPSS rescore
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 14:56 UTCEPSS rescore
Show 75 more
  1. 2026-08-16 10:47 UTCGHSA enrichment
  2. 2026-08-16 07:03 UTCEG score recompute
  3. 2026-08-16 07:03 UTCGHSA enrichment
  4. 2026-08-16 02:15 UTCEPSS rescore
  5. 2026-08-15 01:31 UTCEPSS rescore
  6. 2026-08-14 23:45 UTCGHSA enrichment
  7. 2026-08-14 20:01 UTCGHSA enrichment
  8. 2026-08-14 16:18 UTCGHSA enrichment
  9. 2026-08-14 12:34 UTCGHSA enrichment
  10. 2026-08-14 08:46 UTCGHSA enrichment
  11. 2026-08-14 05:03 UTCEG score recompute
  12. 2026-08-14 05:03 UTCGHSA enrichment
  13. 2026-08-13 22:00 UTCEPSS rescore
  14. 2026-08-13 09:20 UTCGHSA enrichment
  15. 2026-08-13 02:42 UTCGHSA enrichment
  16. 2026-08-12 22:59 UTCGHSA enrichment
  17. 2026-08-12 19:15 UTCEG score recompute
  18. 2026-08-12 19:15 UTCGHSA enrichment
  19. 2026-08-12 13:51 UTCEPSS rescore
  20. 2026-08-11 23:08 UTCGHSA enrichment
  21. 2026-08-11 19:24 UTCEG score recompute
  22. 2026-08-11 19:24 UTCGHSA enrichment
  23. 2026-08-11 06:40 UTCGHSA enrichment
  24. 2026-08-11 02:57 UTCEG score recompute
  25. 2026-08-11 02:57 UTCGHSA enrichment
  26. 2026-08-11 00:00 UTCEPSS rescore
  27. 2026-08-10 11:55 UTCGHSA enrichment
  28. 2026-08-10 07:27 UTCGHSA enrichment
  29. 2026-08-10 03:43 UTCGHSA enrichment
  30. 2026-08-09 23:59 UTCGHSA enrichment
  31. 2026-08-09 20:16 UTCGHSA enrichment
  32. 2026-08-09 16:32 UTCEG score recompute
  33. 2026-08-09 16:32 UTCGHSA enrichment
  34. 2026-08-09 13:47 UTCEPSS rescore
  35. 2026-08-09 12:49 UTCGHSA enrichment
  36. 2026-08-09 08:13 UTCGHSA enrichment
  37. 2026-08-09 04:29 UTCEG score recompute
  38. 2026-08-09 04:29 UTCGHSA enrichment
  39. 2026-08-08 16:37 UTCEPSS rescore
  40. 2026-08-08 08:57 UTCGHSA enrichment
  41. 2026-08-08 05:14 UTCGHSA enrichment
  42. 2026-08-08 01:30 UTCGHSA enrichment
  43. 2026-08-07 21:47 UTCGHSA enrichment
  44. 2026-08-07 18:03 UTCEG score recompute
  45. 2026-08-07 18:03 UTCGHSA enrichment
  46. 2026-08-07 14:20 UTCGHSA enrichment
  47. 2026-08-06 17:31 UTCEG score recompute
  48. 2026-08-06 17:31 UTCGHSA enrichment
  49. 2026-08-06 13:47 UTCEPSS rescore
  50. 2026-08-06 12:40 UTCGHSA enrichment
  51. 2026-08-06 07:08 UTCGHSA enrichment
  52. 2026-08-06 03:24 UTCGHSA enrichment
  53. 2026-08-05 23:41 UTCEG score recompute
  54. 2026-08-05 23:41 UTCGHSA enrichment
  55. 2026-08-05 19:17 UTCEPSS rescore
  56. 2026-08-05 19:17 UTCEPSS rescore
  57. 2026-08-04 15:10 UTCEPSS rescore
  58. 2026-08-04 10:39 UTCEPSS rescore
  59. 2026-08-04 05:40 UTCGHSA enrichment
  60. 2026-08-04 01:39 UTCGHSA enrichment
  61. 2026-08-03 21:56 UTCEG score recompute
  62. 2026-08-03 21:56 UTCGHSA enrichment
  63. 2026-08-03 10:36 UTCEPSS rescore
  64. 2026-08-03 00:59 UTCGHSA enrichment
  65. 2026-08-02 21:15 UTCGHSA enrichment
  66. 2026-08-02 17:32 UTCGHSA enrichment
  67. 2026-08-02 13:47 UTCEG score recompute
  68. 2026-08-02 13:47 UTCGHSA enrichment
  69. 2026-08-02 02:27 UTCEPSS rescore
  70. 2026-08-01 04:16 UTCEPSS rescore
  71. 2026-07-30 16:28 UTCEPSS rescore
  72. 2026-07-30 01:30 UTCEPSS rescore
  73. 2026-07-28 15:37 UTCEPSS rescore
  74. 2026-07-27 14:14 UTCEPSS rescore
  75. 2026-07-26 14:54 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-6068?
CVE-2026-6068 is a critical vulnerability published on April 10, 2026. 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…
When was CVE-2026-6068 disclosed?
CVE-2026-6068 was first published in the National Vulnerability Database on April 10, 2026, with the most recent update on May 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6068 actively exploited?
CVE-2026-6068 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 64.0% of all scored CVEs.
What is the CVSS score of CVE-2026-6068?
CVE-2026-6068 has a CVSS v3 base score of 9.6 (NVD).
How do I remediate CVE-2026-6068?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6068, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-6068

Explore →

Is Your Infrastructure Affected by CVE-2026-6068?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs