CVE-2026-54271

HIGHPre-NVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 86% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.2Exploit: NoneExposed: 0

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

protobufjs-cli is the command line add-on for protobuf.js. Prior to 1.3.2 and 2.5.0, a previous fix for unsafe name handling in pbjs static / static-module code generation was incomplete. Affected versions of protobufjs-cli could still emit unsafe JavaScript references when generating static output from crafted JSON descriptor input. The common case of parsing schemas from .proto files is not affected. This is a bypass of CVE-2026-44295. An attacker who can provide or influence pre-parsed JSON descriptors passed to pbjs static code generation may be able to cause generated JavaScript output to contain attacker-controlled code. The injected code may execute if the generated file is later executed or imported and an affected generated API path is invoked. This vulnerability is fixed in 1.3.2 and 2.5.0.

CVSS v3
8.2
EG Score
8.2(medium)
EPSS
13.6%
KEV
Not listed

Published

June 15, 2026

Last Modified

June 24, 2026

Advisory Details (1)

Auto-updated Jun 22, 2026
Patch available. Sources: github.
github Patch Available

Code injection in pbjs static output from crafted JSON descriptor names · Advisory · protobufjs/protobuf.js · GitHub

https://github.com/protobufjs/protobuf.js/security/advisories/GHSA-pr59-h9ph-3fr8

Vendor Advisories for CVE-2026-54271(1)

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

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
protobufjs-cli—2.5.0—

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54271?
CVE-2026-54271 is a high vulnerability published on June 15, 2026. protobufjs-cli is the command line add-on for protobuf.js. Prior to 1.3.2 and 2.5.0, a previous fix for unsafe name handling in pbjs static / static-module code generation was incomplete. Affected versions of protobufjs-cli could still emit unsafe JavaScript references when generating static output…
When was CVE-2026-54271 disclosed?
CVE-2026-54271 was first published in the National Vulnerability Database on June 15, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54271 actively exploited?
CVE-2026-54271 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 13.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54271?
CVE-2026-54271 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-54271?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54271, 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-54271

Explore →

Is Your Infrastructure Affected by CVE-2026-54271?

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

Start Free Scan →Browse All CVEs