CVE-2025-32781

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-07-13. the CNA's CVSS baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:github_m, ghsa
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: —CVSS: 6.5Exploit: NoneExposed: 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)
EPSS
—
KEV
Not listed

Published

July 13, 2026

Last Modified

July 15, 2026

References (4)

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.

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 6× 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-15 13:35 UTCEG score recompute
  2. 2026-07-15 13:35 UTCGHSA enrichment
  3. 2026-07-14 15:22 UTCEG score recompute
  4. 2026-07-14 15:22 UTCGHSA enrichment
  5. 2026-07-13 17:08 UTCEG score recompute
  6. 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(4)

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.
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

Explore the affected products and dependency analysis for 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