CVE-2026-59954
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 configuration data when AccessKey or management key authentication is enabled because ConfigService can accept a non-canonical appId variant during authentication while downstream request handling resolves it to the protected app, including accent variants under accent-insensitive collations or trailing-space variants under PAD SPACE collations on /configs and /configfiles endpoints. 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 before 2.5.2 has an authentication bypass via non-canonical appId variants. The authentication layer accepts appId representations with accent differences (accent-insensitive collations) or trailing spaces (PAD SPACE collations), but downstream processing resolves these to the protected application, allowing unauthorized access to /configs and /configfiles endpoints.
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 versionCheck the Apollo ConfigService version by reviewing the startup logs, the built-in /env endpoint, or the about.json file typically located at /opt/apollo-configservice or within the JAR's version properties. If using Docker, check the image tag or inspect the container metadata.Affected if The installed version is before 2.5.2 (e.g., 2.5.1, 2.5.0, 2.4.x, or earlier)
-
Verify authentication is enabledReview the Apollo configuration files (typically application.properties or application.yml) for the property 'apollo.portal.env=pro' or similar authentication-related settings. Confirm that the portal or config service has authentication enforcement configured.Affected if Authentication is enforced (the vulnerability only matters if auth is enabled; if auth is disabled, the bypass has no impact)
-
Confirm exposed endpointsInspect network exposure or API gateway configuration to determine if the /configs and /configfiles REST endpoints of the ConfigService are accessible over the network. Check for any path mappings in the deployed application's context.Affected if The /configs or /configfiles endpoints are exposed and reachable from untrusted networks
-
Test for variant appId bypassUsing a tool like curl, attempt an authenticated request to /configs or /configfiles with a variant appId: (1) use an appId with accented characters (e.g., 'appId' with 'é' instead of 'e') that normalizes to the protected appId, or (2) use an appId with trailing spaces (e.g., 'myappId ' with a trailing space). Compare the response to a request with the canonical appId.Affected if Requests with accent-different or trailing-space appIds succeed when they should fail (returning config data for the protected appId instead of a 401/403)
-
Check collation settingsReview the database configuration for the Apollo portal or config service database. Look for collation settings on the App table or relevant columns. Specifically check if the database uses accent-insensitive (accent-insensitive collations like utf8mb4_unicode_ci) or PAD SPACE collations.Affected if The database collation is accent-insensitive or uses PAD SPACE (vulnerability relies on these collation behaviors)
You are affected if Apollo ConfigService is version 2.5.1 or earlier AND authentication is enabled AND the /configs or /configfiles endpoints are exposed AND either accent-insensitive or PAD SPACE database collations are in use.
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, which includes proper validation of appId variants during authentication to prevent bypass.
2.5.2
- 1. Identify the current Apollo ConfigService version in use by checking the deployment configuration or running `apollo-configservice --version` if the binary supports version reporting
- 2. Confirm the deployment uses AccessKey or management key authentication for the /configs and /configfiles endpoints, as this vulnerability only affects authenticated endpoints
- 3. Back up all Apollo configuration data, database schemas, and deployment configurations before upgrading
- 4. Upgrade Apollo ConfigService to version 2.5.2 or later by updating the Docker image, JAR artifact, or Helm chart to the corresponding version tag
- 5. After upgrading, verify that non-canonical appId variants (accent-insensitive or trailing-space variants) are now rejected at authentication by testing with malformed appId inputs
- 6. Monitor ConfigService logs for any authentication failures or unexpected behavior after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-59954 — 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-59954 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