dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-22739

HIGH · 8.6 CVSS v3.1 Published 2026-03-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Path traversal vulnerability in Spring Cloud Config Server when using native file system backend. The profile parameter from requests is not properly validated, allowing attackers to access files outside configured search directories using directory traversal sequences (e.g., ../../).

MitigationUpgrade Spring Cloud to the fixed versions (3.1.13+, 4.1.9+, 4.2.3+, 4.3.2+, 5.0.2+) or implement strict input validation on the profile parameter to reject path traversal characters before applying the fix.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Spring Cloud Config Server is deployed
    Check for running Java processes with config server JAR, or look for config-server JAR/WAR files in the application directory. Check process list for 'spring-cloud-config-server' or review deployed artifacts.
    Affected if Spring Cloud Config Server is not present in the environment
  2. Determine the installed Spring Cloud Config Server version
    If using a JAR file, check the manifest (jar tf manifest.mf or unzip -p) for Implementation-Version. If running, check the startup logs or /env endpoint for 'spring-cloud-config' version information.
    Affected if The version is before 3.1.13, 4.1.9, 4.2.3, 4.3.2, or 5.0.2 (or cannot be determined)
  3. Verify native file system backend is in use
    Review application.properties or application.yml for 'spring.cloud.config.server.native' configuration. Look for 'spring.cloud.config.server.native.search-locations' property which indicates native file system backend.
    Affected if spring.cloud.config.server.native is enabled or spring.cloud.config.server.native.search-locations is configured
  4. Check the configured search locations
    Examine spring.cloud.config.server.native.search-locations in configuration files or runtime /env endpoint. Note the directories from which Config Server serves configuration files.
    Affected if Search locations are configured and the server uses native file system backend (vulnerable configuration)
  5. Assess network exposure of the Config Server
    Review network listeners, firewall rules, or load balancer configurations to determine if the Config Server REST endpoints are accessible from untrusted networks.
    Affected if Config Server HTTP endpoints are exposed to untrusted/unauthenticated network access

Environment is affected if running a vulnerable Spring Cloud Config Server version (before fixes listed) with native file system backend enabled and exposed to network access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Spring Cloud to the fixed versions (3.1.13+, 4.1.9+, 4.2.3+, 4.3.2+, 5.0.2+) or implement strict input validation on the profile parameter to reject path traversal characters before applying the fix.

Recommended fix High confidence

Spring Cloud 3.1.13+, 4.1.9+, 4.2.3+, 4.3.2+, or 5.0.2+ depending on your Spring Boot compatibility

  1. Identify your current Spring Cloud version by checking your dependency management (e.g., pom.xml, build.gradle)
  2. Determine which Spring Cloud branch is compatible with your Spring Boot version (Spring Cloud 2023.0.x requires Spring Boot 3.2+, 2022.0.x requires Spring Boot 3.0+, etc.)
  3. Upgrade to the minimum fixed version for your branch: for 3.1.x upgrade to 3.1.13+, for 4.1.x upgrade to 4.1.9+, for 4.2.x upgrade to 4.2.3+, for 4.3.x upgrade to 4.3.2+, for 5.0.x upgrade to 5.0.2+
  4. Update your dependency management file (pom.xml or build.gradle) with the new Spring Cloud version
  5. Rebuild and test your application to verify the upgrade works correctly
  6. Verify that the path traversal vulnerability is no longer present by testing that requests with '../' sequences in the profile parameter are rejected
Caveat Upgrading Spring Cloud may require Spring Boot version compatibility checks; review Spring Cloud release train compatibility matrix before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22739 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22739 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data