CVE-2026-59955
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedApollo 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApollo ConfigService prior to 2.5.2 contains an authentication bypass vulnerability where requests to /configfiles/raw/{appId}/{clusterName}/{namespace} incorrectly parse 'raw' as the appId for AccessKey lookup instead of the actual appId. This causes the system to verify signatures against the wrong credentials, potentially allowing unauthorized access to raw configuration data without proper authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Apollo ConfigService versionLocate the Apollo ConfigService installation and check the version manifest or build metadata. Common locations include the configservice jar filename, a version file, or the startup logs showing the version number.Affected if Version is prior to 2.5.2 (e.g., 2.5.1, 2.5.0, earlier releases)
-
Verify ConfigService is runningIdentify the ConfigService process or container. Check process list, container runtime, or service manager for apollo-configservice or similar process names.Affected if ConfigService is actively running and accessible on the network
-
Confirm /configfiles/raw/ endpoint is accessibleSend a test request to the /configfiles/raw/{appId}/{clusterName}/{namespace} endpoint. Use the literal path 'raw' as the appId segment to observe if the application accepts it without rejecting the malformed path.Affected if The endpoint responds (even with an error) indicating the URL path is being processed rather than rejected at the routing layer
-
Check if AccessKey authentication is in useReview Apollo configuration for AccessKey settings in the database (e.g., AccessKey table) or in ConfigService configuration files. Determine whether AccessKey-based authentication is enabled for config access.Affected if AccessKey authentication is configured and the system attempts signature verification on config requests
-
Assess network exposure of ConfigServiceCheck firewall rules, network policies, or load balancer configuration to determine if the ConfigService port (typically 8080 or 8090) is exposed to untrusted networks or the internet.Affected if ConfigService is reachable from networks outside the trusted administrative boundary
The environment is affected if Apollo ConfigService version is prior to 2.5.2 and the /configfiles/raw/ endpoint is accessible, as the authentication bypass allows signature verification against the wrong AccessKey.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade Apollo to version 2.5.2 or later. If immediate upgrade is not possible, restrict network access to ConfigService endpoints and implement additional access controls.
2.5.2
- 1. Identify the current Apollo ConfigService version by checking the deployed JAR or container image tag
- 2. Stop the Apollo ConfigService instance or cluster
- 3. Backup the current configuration database and any custom configurations
- 4. Replace the Apollo ConfigService binary/JAR with version 2.5.2
- 5. Restart the ConfigService and verify startup completes without errors
- 6. Verify that authentication now correctly parses the appId from the URL path /configfiles/raw/{appId}/{clusterName}/{namespace}
- 7. Test that AccessKey authentication works properly for raw configuration file endpoints
- 8. Confirm unauthorized access to raw configuration data is now blocked
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,048.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-59955 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-59955 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data