CVE-2026-59955

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.5EG
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.5Exploit: None knownExposed: 0

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

Apollo is a reliable configuration management system suitable for microservice configuration management scenarios. Prior to 2.5.2, Apollo ConfigService may allow unauthorized access to raw configuration data when AccessKey or management key authentication is enabled because requests under /configfiles/raw/{appId}/{clusterName}/{namespace} are parsed for authentication as appId raw instead of the actual path appId, causing ConfigService to look up AccessKey secrets for raw before verifying the request signature and potentially continue without signature verification for the target appId. This issue is fixed in version 2.5.2.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
33%
KEV
Not listed

Published

July 13, 2026

Last Modified

July 15, 2026

Advisory Details (3)

Auto-updated Jul 15, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

Apollo ConfigService access key authentication bypass via raw config file appId parsing · Advisory · apolloconfig/apollo · GitHub

https://github.com/apolloconfig/apollo/security/advisories/GHSA-h4pc-58cc-hc95
github_release Patch Available

Apollo 2.5.2 Release

Patch available: apolloconfig/apollo v2.5.2

https://github.com/apolloconfig/apollo/releases/tag/v2.5.2
github_commit

commit 310809d557e0 (apolloconfig/apollo)

Fix landed in apolloconfig/apollo commit 310809d557e0 — awaiting tagged release

https://github.com/apolloconfig/apollo/commit/310809d557e01c6803051736cd525e333ffe00ec

Vendor Advisories for CVE-2026-59955(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 / EcosystemFixed in / PatchReleasedSource
mavencom.ctrip.framework.apollo:apollo—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

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
com.ctrip.framework.apollo:apollo1.0.0 ... 2.0.1 (19 versions)——

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 20× in last 7d / 33× 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-27 14:14 UTCEPSS rescore
  2. 2026-07-27 09:47 UTCGHSA enrichment
  3. 2026-07-26 22:50 UTCEG score recompute
  4. 2026-07-26 22:50 UTCGHSA enrichment
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-26 11:52 UTCEG score recompute
  8. 2026-07-26 11:52 UTCGHSA enrichment
  9. 2026-07-25 14:18 UTCEPSS rescore
  10. 2026-07-25 14:18 UTCEPSS rescore
  11. 2026-07-24 14:18 UTCEPSS rescore
  12. 2026-07-24 14:18 UTCEPSS rescore
  13. 2026-07-23 14:18 UTCEPSS rescore
  14. 2026-07-23 14:18 UTCEPSS rescore
  15. 2026-07-23 03:21 UTCEG score recompute
  16. 2026-07-22 14:08 UTCEPSS rescore
  17. 2026-07-22 14:08 UTCEPSS rescore
  18. 2026-07-21 15:25 UTCEPSS rescore
  19. 2026-07-21 15:25 UTCEPSS rescore
  20. 2026-07-20 17:08 UTCEPSS rescore
  21. 2026-07-19 14:31 UTCEPSS rescore
  22. 2026-07-19 02:29 UTCEPSS rescore
  23. 2026-07-18 10:04 UTCEPSS rescore
  24. 2026-07-16 23:51 UTCGHSA enrichment
  25. 2026-07-16 17:03 UTCEPSS rescore
Show 8 more
  1. 2026-07-16 12:54 UTCGHSA enrichment
  2. 2026-07-16 01:57 UTCGHSA enrichment
  3. 2026-07-15 15:00 UTCGHSA enrichment
  4. 2026-07-15 04:01 UTCGHSA enrichment
  5. 2026-07-14 17:04 UTCGHSA enrichment
  6. 2026-07-14 06:06 UTCGHSA enrichment
  7. 2026-07-13 19:08 UTCEG score recompute
  8. 2026-07-13 19:08 UTCGHSA enrichment

Related CVEs(same product + same CWE)

Same product

3 shown

maven:com.ctrip.framework.apollo:apollo

Frequently asked(5)

What is CVE-2026-59955?
CVE-2026-59955 is a high vulnerability published on July 13, 2026. Apollo is a reliable configuration management system suitable for microservice configuration management scenarios. Prior to 2.5.2, Apollo ConfigService may allow unauthorized access to raw configuration data when AccessKey or management key authentication is enabled because requests under…
When was CVE-2026-59955 disclosed?
CVE-2026-59955 was first published in the National Vulnerability Database on July 13, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59955 actively exploited?
CVE-2026-59955 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 66.5% of all scored CVEs.
What is the CVSS score of CVE-2026-59955?
CVE-2026-59955 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-59955?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59955, 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-59955

Explore →

Is Your Infrastructure Affected by CVE-2026-59955?

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

Start Free Scan →Browse All CVEs