CVE-2026-54467

HIGHPre-NVD 7.07.0—
EchelonGraph scoreHIGH confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-09-09. a secondary CVSS source baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.0Exploit: None knownExposed: 0

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

On the Trusted Firmware-M (TF-M) 2 through 2.3.0 platform before 00d1b3e, mailbox initialization on PSOC64 and RP2350 accepts a non-secure, unvalidated, supplied pointer.

CVSS v3
7.0
EG Score
7.0(high)
EG Risk
32(Track)
EG Risk 32/100SSVC: Track

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
Severity70% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

August 26, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Aug 26, 2026
No patch confirmed yet.
generic
https://review.trustedfirmware.org/c/TF-M/trusted-firmware-m/+/53051/1/docs/security/security_advisories/missing_ns_pointer_validation_mailbox_init.rst#58
generic

TrustedFirmware-M (TF-M)

https://www.trustedfirmware.org/projects/tf-m/

Vendor Advisories for CVE-2026-54467(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 26× in last 7d / 64× 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-09-19 06:40 UTCEG score recompute
  2. 2026-09-19 06:40 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-18 17:52 UTCGHSA enrichment
  5. 2026-09-18 05:04 UTCEG score recompute
  6. 2026-09-18 05:04 UTCGHSA enrichment
  7. 2026-09-17 19:31 UTCEPSS rescore
  8. 2026-09-17 16:16 UTCGHSA enrichment
  9. 2026-09-17 03:28 UTCGHSA enrichment
  10. 2026-09-16 14:40 UTCEG score recompute
  11. 2026-09-16 14:40 UTCGHSA enrichment
  12. 2026-09-16 14:08 UTCEPSS rescore
  13. 2026-09-16 05:15 UTCEPSS rescore
  14. 2026-09-16 01:47 UTCGHSA enrichment
  15. 2026-09-15 12:59 UTCEG score recompute
  16. 2026-09-15 12:59 UTCGHSA enrichment
  17. 2026-09-15 03:11 UTCEPSS rescore
  18. 2026-09-15 00:11 UTCGHSA enrichment
  19. 2026-09-14 11:22 UTCGHSA enrichment
  20. 2026-09-13 22:34 UTCEG score recompute
  21. 2026-09-13 22:34 UTCGHSA enrichment
  22. 2026-09-13 16:47 UTCEPSS rescore
  23. 2026-09-13 09:46 UTCGHSA enrichment
  24. 2026-09-12 20:59 UTCEG score recompute
  25. 2026-09-12 20:59 UTCGHSA enrichment
Show 39 more
  1. 2026-09-12 08:11 UTCGHSA enrichment
  2. 2026-09-11 19:22 UTCEG score recompute
  3. 2026-09-11 19:22 UTCGHSA enrichment
  4. 2026-09-11 14:53 UTCEPSS rescore
  5. 2026-09-11 06:34 UTCGHSA enrichment
  6. 2026-09-10 17:46 UTCEG score recompute
  7. 2026-09-10 17:46 UTCGHSA enrichment
  8. 2026-09-10 09:35 UTCEPSS rescore
  9. 2026-09-10 04:58 UTCEG score recompute
  10. 2026-09-10 04:58 UTCGHSA enrichment
  11. 2026-09-09 00:54 UTCEG score recompute
  12. 2026-09-08 22:01 UTCEPSS rescore
  13. 2026-09-08 04:42 UTCEG score recompute
  14. 2026-09-07 16:01 UTCEPSS rescore
  15. 2026-09-06 14:18 UTCEG score recompute
  16. 2026-09-06 13:47 UTCEPSS rescore
  17. 2026-09-06 01:30 UTCEG score recompute
  18. 2026-09-04 23:52 UTCEG score recompute
  19. 2026-09-04 11:04 UTCEG score recompute
  20. 2026-09-04 05:06 UTCEPSS rescore
  21. 2026-09-02 20:36 UTCEG score recompute
  22. 2026-09-02 14:12 UTCEPSS rescore
  23. 2026-09-01 18:56 UTCEG score recompute
  24. 2026-09-01 13:54 UTCEPSS rescore
  25. 2026-09-01 06:07 UTCEG score recompute
  26. 2026-09-01 04:40 UTCEPSS rescore
  27. 2026-08-31 03:15 UTCEG score recompute
  28. 2026-08-30 19:17 UTCEPSS rescore
  29. 2026-08-30 01:39 UTCEG score recompute
  30. 2026-08-30 01:22 UTCEPSS rescore
  31. 2026-08-28 23:59 UTCEG score recompute
  32. 2026-08-28 21:41 UTCEPSS rescore
  33. 2026-08-27 18:07 UTCEG score recompute
  34. 2026-08-27 14:25 UTCEPSS rescore
  35. 2026-08-26 15:56 UTCEG score recompute
  36. 2026-08-26 14:46 UTCEPSS rescore
  37. 2026-08-26 14:23 UTCEG score recompute
  38. 2026-08-26 04:20 UTCEG score recompute
  39. 2026-08-26 04:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-54467?
CVE-2026-54467 is a high vulnerability published on August 26, 2026. On the Trusted Firmware-M (TF-M) 2 through 2.3.0 platform before 00d1b3e, mailbox initialization on PSOC64 and RP2350 accepts a non-secure, unvalidated, supplied pointer.
When was CVE-2026-54467 disclosed?
CVE-2026-54467 was first published in the National Vulnerability Database on August 26, 2026, with the most recent update on September 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54467 actively exploited?
CVE-2026-54467 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 95.4% of all scored CVEs.
What is the CVSS score of CVE-2026-54467?
CVE-2026-54467 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2026-54467?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54467, 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

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

Explore →

Is Your Infrastructure Affected by CVE-2026-54467?

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

Start Free Scan →Browse All CVEs