CVE-2026-54679

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 99% 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, nvd
Trending — 3 sources updated this week
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

A fix is available — apply it.

jq is a command-line JSON processor. Prior to 1.8.2, on 32bit system, jvp_string_append has a chance of integer/multiple overflowing and then causing a massive buffer overrun. This vulnerability is fixed in 1.8.2.

CVSS v3
5.5
EG Score
5.5(medium)
EPSS
1.2%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Jun 25, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

potential integer overflow in jvp_string_append · Advisory · jqlang/jq · GitHub

https://github.com/jqlang/jq/security/advisories/GHSA-29gj-222p-j7vx

Vendor Advisories for CVE-2026-54679(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatjq-main-1.8.2-0.1.hum12026-06-25redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 34× 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-06 07:31 UTCEG score recompute
  2. 2026-07-06 07:31 UTCVendor advisory
  3. 2026-07-05 08:37 UTCEG score recompute
  4. 2026-07-05 08:37 UTCVendor advisory
  5. 2026-07-05 02:31 UTCEPSS rescore
  6. 2026-07-05 02:30 UTCEPSS rescore
  7. 2026-07-04 09:44 UTCEG score recompute
  8. 2026-07-04 09:44 UTCVendor advisory
  9. 2026-07-04 06:31 UTCEPSS rescore
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-03 10:52 UTCEG score recompute
  12. 2026-07-03 10:52 UTCVendor advisory
  13. 2026-07-02 11:59 UTCEG score recompute
  14. 2026-07-02 11:59 UTCVendor advisory
  15. 2026-07-01 15:07 UTCEPSS rescore
  16. 2026-07-01 13:07 UTCEG score recompute
  17. 2026-07-01 13:07 UTCVendor advisory
  18. 2026-06-30 23:22 UTCEPSS rescore
  19. 2026-06-30 14:14 UTCEG score recompute
  20. 2026-06-30 14:14 UTCVendor advisory
  21. 2026-06-29 15:20 UTCEG score recompute
  22. 2026-06-29 15:20 UTCVendor advisory
  23. 2026-06-28 16:27 UTCEG score recompute
  24. 2026-06-28 16:27 UTCVendor advisory
  25. 2026-06-28 14:07 UTCEPSS rescore
Show 9 more
  1. 2026-06-28 04:56 UTCEPSS rescore
  2. 2026-06-28 04:56 UTCEPSS rescore
  3. 2026-06-27 17:35 UTCEG score recompute▼ 1.40
  4. 2026-06-27 17:35 UTCVendor advisory
  5. 2026-06-27 03:08 UTCEPSS rescore
  6. 2026-06-26 19:41 UTCNVD updateCVSS v3 → 5.5
  7. 2026-06-26 18:43 UTCEG score recompute
  8. 2026-06-25 19:50 UTCEG score recompute
  9. 2026-06-25 19:49 UTCNVD updatefirst tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-54679?
CVE-2026-54679 is a medium vulnerability published on June 25, 2026. jq is a command-line JSON processor. Prior to 1.8.2, on 32bit system, jvpstringappend has a chance of integer/multiple overflowing and then causing a massive buffer overrun. This vulnerability is fixed in 1.8.2.
When was CVE-2026-54679 disclosed?
CVE-2026-54679 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 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-54679 actively exploited?
CVE-2026-54679 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-54679?
CVE-2026-54679 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-54679?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54679, 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-54679

Explore →

Is Your Infrastructure Affected by CVE-2026-54679?

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

Start Free Scan →Browse All CVEs