Vulnerabilities in pkg:maven/com.ctrip.framework.apollo/apollo
PACKAGECVE-2026-59954 is a HIGH (CVSS 7.5) authentication bypass vulnerability (CWE-287: Improper Authentication) affecting Apollo libraries in the Maven ecosystem. The issue involves apollo configservice access key authentication bypass via appid parsing and non-canonical matching. Remediation is available in the latest vendor maintenance releases.
pkg:maven/com.ctrip.framework.apollo/apollo
Vulnerability advisories affecting package pkg:maven/com.ctrip.framework.apollo/apollo. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-4w3q-qpfq-v992 | CVE-2026-59954 | HIGH | Apollo ConfigService access key authentication bypass via appId parsing and non-canonical matching |
| GHSA-jxpj-9j24-w337 | CVE-2025-32781 | MODERATE | Apollo Portal: There is a risk of unauthorized access to the Apollo configuration center |
| GHSA-h4pc-58cc-hc95 | CVE-2026-59955 | HIGH | Apollo ConfigService access key authentication bypass via raw config file appId parsing |
| GHSA-368x-wmmg-hq5c | CVE-2023-25570 | HIGH | Apollo has potential access control security issue in eureka |
| GHSA-c6c3-h4f7-3962 | CVE-2024-43397 | MODERATE | apollo-portal has potential unauthorized access issue |
| GHSA-fvx3-g627-phm2 | CVE-2019-10686 | CRITICAL | Server-Side Request Forgery (SSRF) in com.ctrip.framework.apollo:apollo |
| GHSA-fmxq-v8mg-qh25 | CVE-2023-25569 | MODERATE | apollo-portal has potential CSRF issue |
CVE-2026-59954 at a Glance
Security Impact
CVSS: 7.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).
How to Fix CVE-2026-59954
To remediate this vulnerability, upgrade all affected Apollo dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>com.ctrip.framework.apollo</groupId>
<artifactId>apollo</artifactId>
<version>Latest secure release</version>
</dependency>
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=com.ctrip.framework.apollo
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-59954, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=com.ctrip.framework.apollo
Analyze the terminal output to locate any version of Apollo in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.
Note: The mvn dependency:tree -Dincludes=com.ctrip.framework.apollo command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-287: Improper Authentication, where when an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. In Apollo, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-59954 Affected Apollo Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
com.ctrip.framework.apollo:apollo
|
Maven |
≤ 2.0.1
|
|
References
Frequently Asked Questions
What is CVE-2026-59954?
Which Apollo versions are affected?
What version fixes CVE-2026-59954?
Is apollo affected?
What is the CVSS score of CVE-2026-59954?
What CWE is associated with CVE-2026-59954?
How can I check Maven dependencies for CVE-2026-59954?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-4w3q-qpfq-v992",
"modified" : "2026-07-20T19:16:52Z",
"published" : "2026-07-13T18:26:30Z",
"aliases" : [ "CVE-2026-59954" ],
"summary" : "Apollo ConfigService access key authentication bypass via appId parsing and non-canonical matching",
"details" : "### Summary\nApollo ConfigService may allow unauthorized access to configuration data when AccessKey / management key authentication is enabled and ConfigService accepts a non-canonical appId variant during authentication while downstream request handling resolves it to the protected app.\n\n### Details\nConfigService extracts appId from configuration and notification requests and uses the extracted value to look up available AccessKey secrets. If the extracted appId is a non-canonical variant that does not exactly match the AccessKey cache key, ConfigService may treat the request as having no available secrets and allow it to continue without signature verification.\n\nThis can happen when downstream release lookup still matches the real appId under database collations that treat the values as equivalent. Examples include accent variants under accent-insensitive collations, or trailing-space variants under PAD SPACE collations.\n\n### Impact\nAn unauthenticated remote attacker may read configuration data from affected ConfigService endpoints when AccessKey / management key authentication is enabled for the target app and the deployment database collation treats a non-canonical appId variant as equivalent to the real appId.\n\n### Affected endpoints\nThe primary impact is on ConfigService configuration read endpoints under /configs and /configfiles. Notification endpoints using appId parameters are also hardened as defense-in-depth.\n\n### Status\nFixed in Apollo 2.5.2. Users should upgrade to Apollo 2.5.2 or later.\n\n### Related advisory\nThe raw config file endpoint parsing issue originally described in this advisory has been split into GHSA-h4pc-58cc-hc95 so each independently fixable vulnerability can receive its own CVE.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "com.ctrip.framework.apollo:apollo"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"last_affected" : "2.0.1"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/apolloconfig/apollo/security/advisories/GHSA-4w3q-qpfq-v992"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-59954"
}, {
"type" : "WEB",
"url" : "https://github.com/apolloconfig/apollo/commit/310809d557e01c6803051736cd525e333ffe00ec"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/apolloconfig/apollo"
}, {
"type" : "WEB",
"url" : "https://github.com/apolloconfig/apollo/releases/tag/v2.5.2"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-20", "CWE-287" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-07-13T18:26:30Z",
"nvd_published_at" : "2026-07-15T17:16:50Z"
}
}