Skip to content
major vulnerability· requires attention

Widely used Spring Cloud Config Server; path traversal allows reading arbitrary local files, impacting many enterprises.

Cloud

CVE-2026-22739

8.6
High
EPSS 1%Patch availableMar 24, 2026

Path traversal in Spring Cloud Config Server enables reading arbitrary local files

common questions

Is CVE-2026-22739 being exploited?

Not confirmed. CVE-2026-22739 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.2% probability of exploitation in the next 30 days.

How severe is CVE-2026-22739?

CVE-2026-22739 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-22739?

Yes. A fix has been recorded for CVE-2026-22739. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-22739 affect?

CVE-2026-22739 affects Spring Cloud Config Server (native filesystem backend) - affected versions: 3.1.x < 3.1.13; 4.1.x < 4.1.9; 4.2.x < 4.2.3; 4.3.x < 4.3.2; 5.0.x < 5.0.2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-22739?

Upgrade to fixed versions: 3.1.13+, 4.1.9+, 4.2.3+, 4.3.2+, 5.0.2+

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Spring Cloud Config Server (native filesystem backend) - affected versions: 3.1.x < 3.1.13; 4.1.x < 4.1.9; 4.2.x < 4.2.3; 4.3.x < 4.3.2; 5.0.x < 5.0.2
impact

Arbitrary local file read via crafted profile param; may expose sensitive configs or system files

action required

Patch when possible

affected versions
Spring Spring Cloud
  • affected>= 3.1.x and < 3.1.13
  • affected>= 4.1.x and < 4.1.9
  • affected>= 4.2.x and < 4.2.3
  • affected>= 4.3.x and < 4.3.2
  • affected>= 5.0.x and < 5.0.2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free