CVE-2026-55588

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (45th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 2.0 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-08-28) is not newer than that change (2026-09-09), so it does not.

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

Also known asEUVD-2026-66110 (ENISA EUVD) · GHSA-298f-872v-2rcx (GitHub Security Advisories) · GO-2026-6317 (OSV.dev)Source: ENISA EUVD

6.5EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

ORAS (OCI Registry As Storage) is a CLI and library for managing artifacts in OCI registries. In ORAS CLI versions up to and including 1.3.2, the recursive referrer traversal does not track visited descriptors, so a malicious OCI registry that returns a cyclic referrer graph causes unbounded recursion and memory growth. This affects oras discover, whose recursive traversal is enabled by default because the --depth option defaults to 0 (unlimited), as well as the recursive referrer counting used by the oras backup and oras restore workflows. A cyclic graph can be as simple as A referring to B and B referring back to A. A malicious registry can use this to cause a client-side denial of service, exhausting CPU and memory and hanging automation or CI/CD pipelines that run ORAS against untrusted registry metadata. The vulnerability does not extend to code execution, artifact substitution, or integrity bypass. This issue has been fixed in version 1.3.3.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/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)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (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.
EPSS PROB
0.5%
EPSS %ILE
45th
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 (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
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 every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade 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 every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (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

August 25, 2026

Last Modified

September 9, 2026

Advisory Details (2)

Auto-updated Aug 25, 2026
Patch available. Sources: github_commit, github.
GitHub commit

commit 440eb65d07a0 (oras-project/oras)

Fix landed in oras-project/oras commit 440eb65d07a0 — awaiting tagged release

https://github.com/oras-project/oras/commit/440eb65d07a0631f131944d28e7c29d562ec17f3
GitHub advisoryMentions a patch (unverified)

Cyclic Referrer Graph Can Cause Unbounded Recursion and Resource Consumption in the ORAS CLI · Advisory · oras-project/oras · GitHub

https://github.com/oras-project/oras/security/advisories/GHSA-298f-872v-2rcx

Vendor Advisories for CVE-2026-55588(1)

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 / EcosystemFix (by version range) / PatchReleasedSource
gooras.land/oras @ 1.3.3 (fixes < 1.3.3)—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
oras1.2.0-1, 1.2.3-1, 1.3.0-1, 1.3.3-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
oras1.2.0-1, 1.2.3-1, 1.3.0-1
  • every version up to 1.3.3-1: fixed in 1.3.3-1
—
Go(1)
PackageVulnerable rangeFix by version rangeDependents
oras.land/oras—
  • every version up to 1.3.3: fixed in 1.3.3
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 46× 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 112 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 12 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% · 45th percentile
  2. 2026-11-01 07:43 UTCGHSA enrichmentGHSA-298f-872v-2rcx · GitHub severity LOW · GitHub CVSS 2.0
  3. 2026-11-01 07:43 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  6. 2026-10-30 10:55 UTCOSV refresh
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  8. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  10. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.5% · 45th percentile
  12. 2026-10-25 14:18 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  14. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  15. 2026-10-22 21:15 UTCEG score recompute
  16. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  19. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  20. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  21. 2026-10-18 03:30 UTCEG score recompute
  22. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  23. 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
Show 75 more
  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  3. 2026-10-12 15:55 UTCEG score recompute
  4. 2026-10-11 19:38 UTCEG score recompute
  5. 2026-10-11 16:54 UTCEG score recompute
  6. 2026-10-11 14:17 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  8. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-10-10 11:11 UTCEG score recompute
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  11. 2026-10-09 03:42 UTCEG score recompute
  12. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  13. 2026-10-08 02:17 UTCEG score recompute
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  15. 2026-10-06 17:39 UTCEG score recompute
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  17. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  18. 2026-10-05 17:11 UTCEG score recompute
  19. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  20. 2026-10-03 16:17 UTCEG score recompute
  21. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  22. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  23. 2026-10-02 07:20 UTCEG score recompute
  24. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-10-01 06:53 UTCEG score recompute
  26. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  27. 2026-09-30 06:23 UTCEG score recompute
  28. 2026-09-29 15:22 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  29. 2026-09-28 23:14 UTCEG score recompute
  30. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  31. 2026-09-27 22:17 UTCEG score recompute
  32. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  33. 2026-09-26 21:38 UTCEG score recompute
  34. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  35. 2026-09-25 04:24 UTCEG score recompute
  36. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  37. 2026-09-24 03:57 UTCEG score recompute
  38. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  39. 2026-09-23 03:25 UTCEG score recompute
  40. 2026-09-22 02:58 UTCEG score recompute
  41. 2026-09-21 02:28 UTCEG score recompute
  42. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  43. 2026-09-20 02:00 UTCEG score recompute
  44. 2026-09-19 01:32 UTCEG score recompute
  45. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  46. 2026-09-18 01:05 UTCEG score recompute
  47. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  48. 2026-09-17 00:37 UTCEG score recompute
  49. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  50. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  51. 2026-09-16 00:09 UTCEG score recompute
  52. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  53. 2026-09-13 23:06 UTCEG score recompute
  54. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  55. 2026-09-12 22:38 UTCEG score recompute
  56. 2026-09-11 22:10 UTCEG score recompute
  57. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  58. 2026-09-10 21:41 UTCEG score recompute
  59. 2026-09-10 09:35 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  60. 2026-09-09 00:57 UTCEG score recompute
  61. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  62. 2026-09-07 22:58 UTCEG score recompute
  63. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  64. 2026-09-06 22:31 UTCEG score recompute
  65. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  66. 2026-09-05 22:03 UTCEG score recompute
  67. 2026-09-04 21:34 UTCEG score recompute
  68. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  69. 2026-09-02 20:37 UTCEG score recompute
  70. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  71. 2026-09-01 20:05 UTCEG score recompute
  72. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  73. 2026-09-01 04:40 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
  74. 2026-08-31 19:35 UTCEG score recompute
  75. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 22nd percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55588?
CVE-2026-55588 is a medium-severity vulnerability; its CVE record was published on August 25, 2026. ORAS (OCI Registry As Storage) is a CLI and library for managing artifacts in OCI registries. In ORAS CLI versions up to and including 1.3.2, the recursive referrer traversal does not track visited descriptors, so a malicious OCI registry that returns a cyclic referrer graph causes unbounded…
When was the CVE record for CVE-2026-55588 published?
The CVE record for CVE-2026-55588 was published on August 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 September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-55588 actively exploited?
CVE-2026-55588 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (45th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-55588?
CVE-2026-55588 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-55588?
A fix for CVE-2026-55588 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-55588 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-55588

Explore →

Is Your Infrastructure Affected by CVE-2026-55588?

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

Book a Demo →Browse All CVEs