CVE-2026-8449

✕ Withdrawn — historical dataUNRATEDCVSS · not yet scored
—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: —CVSS v2: —Exploit: None knownExposed services: Not assessed

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

Rejected reason: This CVE ID has been rejected or withdrawn.

CVSS v3
—
EchelonGraph score
Not yet assessedThis CVE record was withdrawn by its numbering authority, so there is no vulnerability to rate.
EG Score
—
EG Risk
—
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

Published

May 12, 2026

Last Modified

May 13, 2026

Advisory Details (3)

Auto-updated May 12, 2026
No fix on record yet.
generic

Linux ksmbd Remote Memory Corruption via ACL Inheritance | Advisories | VulnCheck

https://www.vulncheck.com/advisories/linux-ksmbd-remote-memory-corruption-via-acl-inheritance
generic

ksmbd: validate inherited ACE SID length · torvalds/linux@996454b · GitHub

https://github.com/torvalds/linux/commit/996454bc0da84d5a1dedb1a7861823087e01a7ae
generic

linux/fs/smb/server/smbacl.c at 6596a02b207886e9e00bb0161c7fd59fea53c081 · torvalds/linux · GitHub

https://github.com/torvalds/linux/blob/6596a02b207886e9e00bb0161c7fd59fea53c081/fs/smb/server/smbacl.c

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 0× in last 7d / 0× 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.

  1. 2026-08-20 21:35 UTCGHSA enrichment
  2. 2026-08-16 04:10 UTCGHSA enrichment
  3. 2026-08-12 15:56 UTCGHSA enrichment
  4. 2026-08-09 04:23 UTCGHSA enrichment
  5. 2026-08-05 21:44 UTCGHSA enrichment
  6. 2026-08-01 21:59 UTCEG score recompute
  7. 2026-08-01 21:59 UTCGHSA enrichment
  8. 2026-07-23 03:23 UTCEG score recompute▼ 8.80
  9. 2026-06-28 12:55 UTCGHSA enrichment
  10. 2026-06-27 23:56 UTCGHSA enrichment
  11. 2026-06-27 09:36 UTCGHSA enrichment
  12. 2026-06-26 20:39 UTCGHSA enrichment
  13. 2026-06-25 20:23 UTCGHSA enrichment
  14. 2026-06-17 14:52 UTCGHSA enrichment
  15. 2026-06-16 22:51 UTCGHSA enrichment
  16. 2026-06-16 03:51 UTCGHSA enrichment
  17. 2026-06-15 01:56 UTCGHSA enrichment
  18. 2026-06-14 12:57 UTCGHSA enrichment
  19. 2026-06-13 23:58 UTCGHSA enrichment
  20. 2026-06-13 04:58 UTCGHSA enrichment
  21. 2026-06-12 14:54 UTCGHSA enrichment
  22. 2026-06-12 01:58 UTCGHSA enrichment
  23. 2026-06-11 13:00 UTCGHSA enrichment
  24. 2026-06-11 00:03 UTCGHSA enrichment
  25. 2026-06-10 11:06 UTCGHSA enrichment
Show 19 more
  1. 2026-06-09 22:10 UTCGHSA enrichment
  2. 2026-06-09 09:04 UTCGHSA enrichment
  3. 2026-06-08 20:05 UTCGHSA enrichment
  4. 2026-06-08 06:37 UTCGHSA enrichment
  5. 2026-06-07 17:41 UTCGHSA enrichment
  6. 2026-06-07 04:44 UTCGHSA enrichment
  7. 2026-06-06 15:48 UTCGHSA enrichment
  8. 2026-06-06 02:51 UTCGHSA enrichment
  9. 2026-06-05 13:54 UTCGHSA enrichment
  10. 2026-06-05 00:57 UTCGHSA enrichment
  11. 2026-06-04 12:00 UTCGHSA enrichment
  12. 2026-06-03 23:03 UTCGHSA enrichment
  13. 2026-06-03 10:06 UTCGHSA enrichment
  14. 2026-06-02 21:08 UTCGHSA enrichment
  15. 2026-06-02 08:10 UTCGHSA enrichment
  16. 2026-06-01 19:13 UTCGHSA enrichment
  17. 2026-06-01 06:16 UTCGHSA enrichment
  18. 2026-05-20 12:39 UTCEG score recompute
  19. 2026-05-20 12:39 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(3)

What is CVE-2026-8449?
CVE-2026-8449 is a publicly disclosed vulnerability published on May 12, 2026. Rejected reason: This CVE ID has been rejected or withdrawn.
When was CVE-2026-8449 disclosed?
CVE-2026-8449 was first published on May 12, 2026, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
How do I remediate CVE-2026-8449?
No fix for CVE-2026-8449 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-8449

Explore →

Is Your Infrastructure Affected by CVE-2026-8449?

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

Book a Demo →Browse All CVEs