# Apollo has potential access control security issue in eureka

Advisory record · `GHSA-368x-wmmg-hq5c`

- **Identifiers:** `GHSA-368x-wmmg-hq5c` · `CVE-2023-25570`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-306](https://cwe.mitre.org/data/definitions/306.html)
- **Tags:** [Authentication bypass](https://agentprime.io/advisories/tag/auth-bypass.md)
- **Published:** 22 Feb 2023
- **Updated:** 9 Jun 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 22 Feb 2023, 21:58 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `com.ctrip.framework.apollo:apollo` (Maven): affected `<2.1.0`; fixed in `2.1.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Apollo package com.ctrip.framework.apollo:apollo, versions before 2.1.0, has an access control issue in its built-in Eureka service, which has no authentication enabled. An attacker who can reach apollo-configservice over the network could access Eureka directly and mock the configservice and adminservice. Upgrade to version 2.1.0, which adds login authentication for Eureka. Without upgrading, do not expose apollo-configservice to the internet.

Written 3 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0082, the 57th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:20 UTC: First seen by agentprime
- 31 Oct 2026, 14:20 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-368x-wmmg-hq5c)

## Sources

- [GitHub Advisory Database: GHSA-368x-wmmg-hq5c](https://github.com/advisories/GHSA-368x-wmmg-hq5c)
- [OSV: GHSA-368x-wmmg-hq5c](https://osv.dev/vulnerability/GHSA-368x-wmmg-hq5c)
- <https://github.com/apolloconfig/apollo/security/advisories/GHSA-368x-wmmg-hq5c>
- <https://nvd.nist.gov/vuln/detail/CVE-2023-25570>
- <https://github.com/apolloconfig/apollo/pull/4663>
- <https://github.com/apolloconfig/apollo/commit/7df79bf8df6960433ed4ff782a54e3dfc74632bd>
- <https://github.com/apolloconfig/apollo>
- <https://github.com/apolloconfig/apollo/releases/tag/v2.1.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-368x-wmmg-hq5c>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-368x-wmmg-hq5c/>. Everything for agents: <https://agentprime.io/llms.txt>.
