CVE-2025-32781

Deferred Deferred - Pending Action

Apollo Portal Configuration Exposure via Release ID

Publication date: 2026-07-15

Last updated on: 2026-07-15

Assigner: GitHub, Inc.

Description

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-15

Last Modified

2026-07-15

Generated

2026-08-05

AI Q&A

2026-07-16

EPSS Evaluated

2026-08-03

NVD

CVE-2025-32781

EUVD

EUVD-2025-210473

Affected Vendors & Products

Vendor	Product	Version / Range
apolloconfig	apollo	to 2.5.0 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-639	The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
CWE-862	The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

Attack-Flow Graph

Executive Summary

This vulnerability in Apollo Portal versions before 2.5.0 allows low-privileged users to access sensitive configuration data of other applications and namespaces by exploiting a missing permission check in the release endpoint. When the configView.memberOnly.envs setting is enabled, an authenticated user can guess or obtain a valid release ID and read configurations without proper authorization.

Detection Guidance

To detect this vulnerability, check if your Apollo Portal version is below 2.5.0 and if the configView.memberOnly.envs setting is enabled. Verify if unauthorized users can access release data via GET /envs/{env}/releases/{releaseId} without proper permission checks.

Impact Analysis

An attacker could read unauthorized configuration data such as credentials or service endpoints, leading to potential data breaches or further exploitation. The vulnerability does not allow modification of configurations or direct impact on system availability.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive data, violating compliance requirements for data protection such as GDPR or HIPAA. Unauthorized exposure of credentials or configuration details may result in regulatory penalties or loss of trust.

Mitigation Strategies

Immediately upgrade Apollo Portal to version 2.5.0 or later. If an upgrade is not feasible, manually apply the permission check fix by ensuring UserPermissionValidator.shouldHideConfigToCurrentUser() is called in the ReleaseController.get method before returning release data.

Hi! I’m here to help you understand CVE-2025-32781. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70