CVE-2025-32781

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-07-13. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.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.0, Apollo Portal does not verify application and namespace permissions when an authenticated user requests a release by ID through GET /envs/{env}/releases/{releaseId} while configView.memberOnly.envs is enabled, allowing a low-privileged Portal user who obtains or guesses a valid releaseId to read configuration data from other applications and namespaces without calling UserPermissionValidator.shouldHideConfigToCurrentUser(...). This issue is fixed in version 2.5.0.

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

Published

July 13, 2026

Last Modified

July 15, 2026

Advisory Details (4)

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

Apollo Portal release endpoint allows cross-application configuration disclosure via releaseId · Advisory · apolloconfig/apollo · GitHub

https://github.com/apolloconfig/apollo/security/advisories/GHSA-jxpj-9j24-w337
github_release Patch Available

Apollo 2.5.0 Release

Patch available: apolloconfig/apollo v2.5.0

https://github.com/apolloconfig/apollo/releases/tag/v2.5.0
github_pr

fix potential access issue

Fix merged in apolloconfig/apollo PR #5378 on 2025-04-11 — awaiting tagged release

https://github.com/apolloconfig/apollo/pull/5378
github_commit

commit 362735ded4f1 (apolloconfig/apollo)

Fix landed in apolloconfig/apollo commit 362735ded4f1 — awaiting tagged release

https://github.com/apolloconfig/apollo/commit/362735ded4f13b62f6ab9df135d7096066e8e291

Vendor Advisories for CVE-2025-32781(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 14× in last 7d / 24× 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:12 UTCEPSS rescore
  2. 2026-07-27 10:07 UTCEG score recompute
  3. 2026-07-27 10:07 UTCGHSA enrichment
  4. 2026-07-26 14:53 UTCEPSS rescore
  5. 2026-07-26 11:53 UTCEG score recompute
  6. 2026-07-26 11:53 UTCGHSA enrichment
  7. 2026-07-25 14:17 UTCEPSS rescore
  8. 2026-07-24 14:17 UTCEPSS rescore
  9. 2026-07-23 02:53 UTCEG score recompute
  10. 2026-07-22 14:07 UTCEPSS rescore
  11. 2026-07-22 14:07 UTCEPSS rescore
  12. 2026-07-21 15:24 UTCEPSS rescore
  13. 2026-07-21 15:24 UTCEPSS rescore
  14. 2026-07-20 17:07 UTCEPSS rescore
  15. 2026-07-19 02:28 UTCEPSS rescore
  16. 2026-07-19 02:28 UTCEPSS rescore
  17. 2026-07-18 10:04 UTCEPSS rescore
  18. 2026-07-18 10:04 UTCEPSS rescore
  19. 2026-07-16 17:02 UTCEPSS rescore
  20. 2026-07-16 11:50 UTCGHSA enrichment
  21. 2026-07-15 13:35 UTCGHSA enrichment
  22. 2026-07-14 15:22 UTCGHSA enrichment
  23. 2026-07-13 17:08 UTCEG score recompute
  24. 2026-07-13 17:07 UTCGHSA enrichment

Related CVEs(same product + same CWE)

Same product

3 shown

maven:com.ctrip.framework.apollo:apollo

Frequently asked(5)

What is CVE-2025-32781?
CVE-2025-32781 is a medium vulnerability published on July 13, 2026. Apollo is a reliable configuration management system suitable for microservice configuration management scenarios. Prior to 2.5.0, Apollo Portal does not verify application and namespace permissions when an authenticated user requests a release by ID through GET /envs/{env}/releases/{releaseId}…
When was CVE-2025-32781 disclosed?
CVE-2025-32781 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-2025-32781 actively exploited?
CVE-2025-32781 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 77.3% of all scored CVEs.
What is the CVSS score of CVE-2025-32781?
CVE-2025-32781 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2025-32781?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-32781, 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-2025-32781

Explore →

Is Your Infrastructure Affected by CVE-2025-32781?

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

Start Free Scan →Browse All CVEs