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)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

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.

What type of vulnerability is CVE-2019-3799?

CVE-2019-3799 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

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

A Nuclei detection template exists for CVE-2019-3799, meaning automated scanners can fingerprint it. A Metasploit module references CVE-2019-3799, which lowers the barrier to weaponization. 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 October 24, 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) Path Traversal vulnerability in org.springframework.cloud:spring-cloud-config-server. 5 public exploit or proof-of-concept references are indexed, 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

Oct 24, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

5 known

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, 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

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

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`

Affected Products

2 products · 4 configurations

Application

communications cloud native core policyoracle

1 version

1.15.0

Application

spring cloud configvmware

≥ 2.1.0 && < 2.1.2

range

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
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

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?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

CWE Classification

Weaponization

Timeline

First exploit

Apr 30, 2019

Disclosed

May 6, 2019

Last updated

Oct 24, 2026

Identifiers

CVE-2019-3799

GHSA-4x49-w62v-76q7

References

Advisorypivotal.io · cve 2019 3799 Advisorynvd.nist.gov · CVE 2019 3799 Fixoracle.com · cpuapr2022 Webgithub.com · CVE 2019 3799

Related vulnerabilities

Also affects spring-cloud-config-server

This CVE is medium severity; 7 of 7 other CVEs affecting spring-cloud-config-server are rated as high or higher (top: critical).

CVE-2026-40981CVE-2026-40982CVE-2026-41002CVE-2026-41004CVE-2026-22739CVE-2020-5410CVE-2020-5405

Same weakness: CWE-22

This CVE is medium severity; 1 of 1 other CVE with CWE-22 is rated as high or higher (top: high).

CVE-2026-62331Browse all CWE-22

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

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

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

How to detect CVE-2019-3799

Frequently Asked Questions

Is CVE-2019-3799 in your dependencies?