Server-Side Request Forgery (SSRF) in com.ctrip.framework.apollo:apollo

published 2019-04-01 7y ago modified 2026-06-17 4mo ago also GHSA-fvx3-g627-phm2 , EUVD-2019-0419

cvss: 10.0; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.6%; EPSS 1.6% chance of exploitation in 30 days, percentile 75%
public exploits: 0; none known

An SSRF vulnerability was found in an API from Ctrip Apollo through 1.4.0-SNAPSHOT. An attacker may use it to do an intranet port scan or raise a GET request via /system-info/health because the %23 substring is mishandled.

Is CVE-2019-10686 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.56% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	10.0	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
NVD	2.0	7.5	AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub	3.0	10.0	CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
maven	com.ctrip.framework.apollo:apollo	<=1.3.0	no fix listed

Classification

Weakness

CWE-918 Server-Side Request Forgery

References

github.com /ctripcorp/apollo/issues/2103
web, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2019-10686
advisory
github.com /advisories/GHSA-fvx3-g627-phm2
advisory
github.com /ctripcorp/apollo
package

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.