CVE-2026-48702

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-25. A secondary CVSS source baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-57928 (ENISA EUVD) · GHSA-47q9-m4ww-924m (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Rekor is a software supply chain transparency log. Starting in version 0.3.0 and prior to version 1.5.2, the Package.Unmarshal() function in pkg/types/alpine/apk.go decompresses the signature and control gzip members of an APK file into in-memory buffers without bounding the total decompressed size. The existing max_apk_metadata_size check (default 1MB) is only applied to individual tar entry header sizes after decompression completes, so it does not prevent a decompression bomb from consuming unbounded heap memory. An attacker can craft a gzip stream that compresses at a ~1000:1 ratio (e.g., 2MB compressed zeros → 2GB decompressed). When submitted as spec.package.content in an Alpine ProposedEntry, the server decompresses the full payload into memory during request processing, triggering a fatal Go runtime out-of-memory error or OS OOM-kill that cannot be caught by the server's recover() middleware. This is reachable via two unauthenticated endpoints, POST /api/v1/log/entries (createLogEntry) and POST /api/v1/log/entries/retrieve (searchLogQuery). Both invoke V001Entry.Canonicalize() → fetchExternalEntities() → apk.Unmarshal(packageData), which performs the unbounded decompression. Version 1.5.2 patches the issue. There is no effective workaround. Setting max_request_body_size reduces but does not eliminate exposure due to the ~1000:1 compression ratio (a 1MB body limit still allows ~1GB heap allocation). Setting max_apk_metadata_size has no effect on this vulnerability since the check is applied after decompression.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 25, 2026

Last Modified

October 23, 2026

Advisory Details (1)

Auto-updated Aug 13, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

OOM condition due to Unbounded gzip decompression in Alpine APK parsing · Advisory · sigstore/rekor · GitHub

https://github.com/sigstore/rekor/security/advisories/GHSA-47q9-m4ww-924m

Vendor Advisories for CVE-2026-48702(5)

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

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhtas/rekor-server-rhel9:17873053972026-08-25redhat
redhatrhtas/rekor-server-rhel9:17853915242026-08-05redhat
redhattrivy-main-0.72.0-0.1.hum12026-07-02redhat
redhatcosign-main-3.1.1-0.1.hum12026-06-10redhat
gogithub.com/sigstore/rekor @ 1.5.2 (fixes >= 0.3.0, < 1.5.2)—ghsa

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.

Affected Packages

(3 across 3 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
rekor1.3.10-1 ... 1.5.3-2 (10 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
rekor1.3.10-1 ... 1.5.1-1 (7 versions)
  • every version up to 1.5.2-1: fixed in 1.5.2-1
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/sigstore/rekor—
  • 0.3.0 up to 1.5.2: fixed in 1.5.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 45× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 178 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 78 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-48702?
CVE-2026-48702 is a high-severity vulnerability; its CVE record was published on June 25, 2026. Rekor is a software supply chain transparency log. Starting in version 0.3.0 and prior to version 1.5.2, the Package.Unmarshal() function in pkg/types/alpine/apk.go decompresses the signature and control gzip members of an APK file into in-memory buffers without bounding the total decompressed…
When was the CVE record for CVE-2026-48702 published?
The CVE record for CVE-2026-48702 was published on June 25, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 23, 2026; the record at its source may have been updated since.
Is CVE-2026-48702 actively exploited?
CVE-2026-48702 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48702?
CVE-2026-48702 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48702?
A fix for CVE-2026-48702 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48702 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-48702?

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

Book a Demo →Browse All CVEs