Atomicorp WAF Research Note: CVE-2026-22739

Spring Cloud Config Server - Path Traversal

CVE Details

• Already protected by existing Atomicorp WAF rules
• Protection status: Understanding Atomicorp WAF Protection Status
• CVE: CVE-2026-22739
• Name: Spring Cloud Config Server - Path Traversal
• Severity: High
• CVSS: 8.6 (v3.1) (High)
• CVSS version: 3.1
• CVSS source: vmware CNA
• CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
  • Attack vector: Network
  • Attack complexity: Low
  • Privileges required: None
  • User interaction: None
  • Scope: Unchanged
  • Confidentiality impact: High
  • Integrity impact: Low
  • Availability impact: Low
• CWE: CWE-22 — Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’)
• Related CAPEC attack patterns (via MITRE CWE relationships): CAPEC-126 (opens in a new tab) , CAPEC-64 (opens in a new tab) , CAPEC-76 (opens in a new tab) , CAPEC-78 (opens in a new tab) , CAPEC-79 (opens in a new tab)
• Vendor: vmware
• Vulnerable product: spring cloud config
• CVE published: 2026-03-24
• CVE last modified: 2026-09-04
• Affected versions (NVD configurations):
  • spring cloud config: < 3.1.13
  • spring cloud config: >= 4.1.0, < 4.1.9
  • spring cloud config: >= 4.2.0, < 4.2.6
  • spring cloud config: >= 4.3.0, < 4.3.2
  • spring cloud config: >= 5.0.0, < 5.0.2
• EPSS: 0.0122; 66.9th percentile (FIRST (opens in a new tab) )
• Latest Update: 2026-08-01
• Selected Rule IDs observed: 346019
• Matching rules: 1; rules with blocking actions: 1
• Would-block Rule IDs: 346019

Vulnerability Description

Vulnerability in Spring Cloud when substituting the profile parameter from a request made to the Spring Cloud Config Server configured to the native file system as a backend, because it was possible to access files outside of the configured search directories.This issue affects Spring Cloud: from 3.1.X before 3.1.13, from 4.1.X before 4.1.9, from 4.2.X before 4.2.3, from 4.3.X before 4.3.2, from 5.0.X before 5.0.2.

Recommended Actions

1. Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (346019 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.

2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

   • Affected versions: Spring Spring Cloud versions earlier than 3.1.13.
   • Affected versions: Spring Spring Cloud versions earlier than 4.1.9.
   • Affected versions: Spring Spring Cloud versions earlier than 4.2.3.
   • Affected versions: Spring Spring Cloud versions earlier than 4.3.2.
   • Affected versions: Spring Spring Cloud versions earlier than 5.0.2.
   • Recommended upgrade: Upgrade Spring Spring Cloud to 3.1.13 or later.
   • Recommended upgrade: Upgrade Spring Spring Cloud to 4.1.9 or later.
   • Recommended upgrade: Upgrade Spring Spring Cloud to 4.2.3 or later.
   • Recommended upgrade: Upgrade Spring Spring Cloud to 4.3.2 or later.
   • Recommended upgrade: Upgrade Spring Spring Cloud to 5.0.2 or later.

3. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

• NVD (opens in a new tab)
• CVE Record (opens in a new tab)
• Vendor advisory: https://spring.io/security/cve-2026-22739 (opens in a new tab)

Test or Research Source

• Source: http/cves/2026/CVE-2026-22739.yaml (opens in a new tab)
• Tags: config-server, cve, cve2026, lfi, spring, spring-cloud, traversal

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

• Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
• Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
• Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
• Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
• Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ (opens in a new tab) .