How severe is CVE-2019-3799?

CVE-2019-3799 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2019-3799?

CVE-2019-3799 affects the following packages: org.springframework.cloud:spring-cloud-config-server (Maven), org.springframework.cloud:spring-cloud-config-server (Maven), org.springframework.cloud:spring-cloud-config-server (Maven). Ecosystems affected: Maven.

How do I fix CVE-2019-3799?

Update org.springframework.cloud:spring-cloud-config-server to 1.4.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-3799 is resolved across your whole dependency graph.

How do I detect CVE-2019-3799 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.cloud:spring-cloud-config-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-3799 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2019-3799?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2019-3799 can be triaged on real exposure rather than presence alone.

Is CVE-2019-3799 actively exploited in the wild?

Yes. There are 5 known exploit references for CVE-2019-3799, including 1 documented proof-of-concept exploit on Exploit-DB and 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2019-3799?

CVE-2019-3799 has an EPSS (Exploit Prediction Scoring System) score of 85.3%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is there exploit tooling available for CVE-2019-3799?

A Nuclei detection template exists for CVE-2019-3799, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2019-3799 published, and has it been updated?

CVE-2019-3799 was published on May 6, 2019 and was last updated on July 8, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2019-3799 — spring-cloud-config-server

MEDIUM

CVE-2019-3799 is a medium-severity (CVSS 6.5) vulnerability in org.springframework.cloud:spring-cloud-config-server. 5 public exploit references exist, so weaponization risk is real. A fix is available for org.springframework.cloud:spring-cloud-config-server — see the affected versions and patch details below.

Path Traversal in Spring Cloud Config

Also known asGHSA-4x49-w62v-76q7

Published

May 6, 2019

Updated

Jul 8, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

5 known

Exploitation data as of Sep 19, 2026 · OSV.dev, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

85.3%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2019-3799 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 376,715 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

3 pkgs affected

☕org.springframework.cloud:spring-cloud-config-server☕org.springframework.cloud:spring-cloud-config-server☕org.springframework.cloud:spring-cloud-config-server

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Spring Cloud Config, versions 2.1.x prior to 2.1.2, versions 2.0.x prior to 2.0.4, and versions 1.4.x prior to 1.4.6, and older unsupported versions allow applications to serve arbitrary configuration files through the spring-cloud-config-server module. A malicious user, or attacker, can send a request using a specially crafted URL that can lead a directory traversal attack.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework.cloud:spring-cloud-config-server`	all versions	1.4.6`org.springframework.cloud:spring-cloud-config-server:1.4.6`
☕Maven	`org.springframework.cloud:spring-cloud-config-server`	≥ 2.0.0&&< 2.0.4	2.0.4`org.springframework.cloud:spring-cloud-config-server:2.0.4`
☕Maven	`org.springframework.cloud:spring-cloud-config-server`	≥ 2.1.0&&< 2.1.2	2.1.2`org.springframework.cloud:spring-cloud-config-server:2.1.2`

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-46772webappsjava

Spring Cloud Config 2.1.x - Path Traversal (Metasploit)

by Dhiraj Mishra · Apr 30, 2019

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.cloud:spring-cloud-config-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework.cloud:spring-cloud-config-server to 1.4.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-3799 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2019-3799 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2019-3799. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

How to detect CVE-2019-3799

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2019-3799 -u https://target

Template: Spring Cloud Config Server - Local File Inclusion
Severity: medium
Impact: An attacker can exploit this vulnerability to read arbitrary files on the server, potentially leading to unauthorized access or sensitive information disclosure.
Remediation: Upgrade to a patched version of Spring Cloud Config Server or apply the recommended security patches.

Template by ProjectDiscovery nuclei-templates (madrobot), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-3799 in your dependencies?

O3 Security finds CVE-2019-3799 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works