CVE-2025-32781

Apollo: Apollo Portal release endpoint allows cross-application configuration disclosure via releaseId

Published Jul 15, 2026 CVSS 3.1 · 6.5 Medium EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Apollo Portal’s release endpoint does not verify application or namespace permissions when a release is requested by ID while the configView.memberOnly.envs setting is enabled. A low‑privileged authenticated user who can guess or obtain a valid releaseId can read configuration data belonging to other applications and namespaces. This leads to unauthorized information disclosure and maps to authorization bypass weaknesses (CWE‑639 and CWE‑862).

Affected Systems

All deployments of apolloconfig:apollo running a version earlier than 2.5.0 with Apollo Portal enabled and configView.memberOnly.envs set to true are affected. The vulnerability arises when the /envs/{env}/releases/{releaseId} endpoint is reachable and users have permission to perform GET requests on release IDs. Any such installation, regardless of the number of applications or namespaces, is at risk if low‑privileged users can access the endpoint.

Risk and Exploitability

The CVSS score of 6.5 signifies moderate severity, while the EPSS score of less than 1 % indicates a low probability of exploitation at present. The vulnerability is not listed in CISA’s KEV catalog. Exploitation guess of a releaseId, with no elevated privileges needed. The likely attack vector is a standard HTTP GET request to /env}.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Apollo to version 2.5.0 or later, which adds the missing permission check.
  • If an upgrade cannot be performed immediately, disable the configView.memberOnly.envs setting to prevent unprivileged users from accessing release IDs of other applications.
  • Enforce stricter permission checks on the /envs/{env}/releases/{releaseId} endpoint, or temporarily block access for users who do not require release reading capabilities until the patch is applied.

Generated by OpenCVE AI on July 31, 2026 at 03:19 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-jxpj-9j24-w337 Apollo Portal: There is a risk of unauthorized access to the Apollo configuration center
History
Type Values Removed Values Added
First Time appeared Apolloconfig
Apolloconfig apollo
Vendors & Products Apolloconfig
Apolloconfig apollo
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title Apollo: Apollo Portal release endpoint allows cross-application configuration disclosure via releaseId
Weaknesses CWE-639
CWE-862
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key

  • CWE-862

    Missing Authorization

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Jul 15, 2026, 5:29 PM
Reserved
Apr 10, 2025, 12:51 PM
Status
Deferred
Published
Jul 15, 2026, 5:16 PM
Modified
Sep 29, 2026, 3:10 PM