{"answers":{"affected":"2 open source packages ship an affected version, including com.ctrip.framework.apollo:apollo.","exploited":"There is no known exploitation of CVE-2026-59954 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-59954 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-59954 is a high-severity authentication bypass vulnerability in apolloconfig apollo, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-59954 and fix it if it is affected.\n\nWhat it is: CVE-2026-59954 is a high-severity authentication bypass vulnerability in apolloconfig apollo, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-59954 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- com.ctrip.framework.apollo:apollo (Maven): affected all versions up to 2.0.1; no fix listed\n- com.ctrip.framework.apollo:apollo (Maven): affected all versions up to 2.0.1; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-59954/ (Markdown: https://insights.sbomify.com/CVE-2026-59954/index.md)","id":"CVE-2026-59954","markdown":"https://insights.sbomify.com/CVE-2026-59954/index.md","name":"CVE-2026-59954","record":{"aliases":["GHSA-4w3q-qpfq-v992"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Apollo configuration server","requires_auth":"none","summary":"Attackers can bypass authentication to read protected configuration data by exploiting non-canonical appId parsing in Apollo ConfigService.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Apollo 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.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Apollo ConfigService access key authentication bypass via appId parsing and non-canonical matching","id":"CVE-2026-59954","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Apollo ConfigService access key authentication bypass via raw config file appId parsing","id":"CVE-2026-59955"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["2.0.1"],"package":"com.ctrip.framework.apollo:apollo","purl":null,"source":"GHSA-4w3q-qpfq-v992"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["2.0.1"],"package":"com.ctrip.framework.apollo:apollo","purl":"pkg:maven/com.ctrip.framework.apollo/apollo","source":"GHSA-4w3q-qpfq-v992"}],"prev":{"headline":"Valibot: record() issue paths can make flatten() throw for inherited Object property names","id":"CVE-2026-59952"},"products":["apollo"],"published":"2026-07-15","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-15","vendors":["apolloconfig"]},"summary":"Attackers can bypass authentication to read protected configuration data by exploiting non-canonical appId parsing in Apollo ConfigService.","url":"https://insights.sbomify.com/CVE-2026-59954/"}