CVE-2026-41002

Protected-file access via clone-directory symlink race

Published May 7, 2026 · Updated May 7, 2026

TOCTOU in Spring Cloud Config Server allows local administrators to read or modify protected data through its Git clone base directory. JGitEnvironmentRepository validates and prepares spring.cloud.config.server.git.basedir, then passes the path to JGit after a window in which the directory can be replaced by a symbolic link. Affected versions are 3.1.0 through 3.1.13, 4.1.0 through 4.1.9, 4.2.0 through 4.2.6, 4.3.0 through 4.3.2, and 5.0.0 through 5.0.2; exploitation requires high local privileges and winning the filesystem race.

CVSS severity7.2
High
EPSS probability0.22%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

TOCTOU in Spring Cloud Config Server allows local administrators to read or modify protected data through its Git clone base directory. JGitEnvironmentRepository validates and prepares spring.cloud.config.server.git.basedir, then passes the path to JGit after a window in which the directory can be replaced by a symbolic link. Affected versions are 3.1.0 through 3.1.13, 4.1.0 through 4.1.9, 4.2.0 through 4.2.6, 4.3.0 through 4.3.2, and 5.0.0 through 5.0.2; exploitation requires high local privileges and winning the filesystem race.

The record

CVE
CVE-2026-41002
Published
May 7, 2026
Updated
May 7, 2026
Vendor
Spring
Product
Spring Cloud Config
Classifications
CWE-367, T1005, T1565.001
Attack vector
local
Privileges
admin

Timeline

How it unfolded

  1. May 7, 2026CVE publishedPublication date reported by the CVE source.
  2. May 7, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=3.1.0 <3.1.14
  2. Affected versionversion=4.1.0 <4.1.10
  3. Affected versionversion=4.2.0 <4.2.7
  4. Affected versionversion=4.3.0 <4.3.3
  5. Affected versionversion=5.0.0 <5.0.3

What conditions does exploitation require?

Attack vectorlocal
Required privilegesadmin

What is affected?

Spring · Spring Cloud Configversion=3.1.0 <3.1.14; version=4.1.0 <4.1.10; version=4.2.0 <4.2.7; version=4.3.0 <4.3.3; version=5.0.0 <5.0.3

Published CVSS scores

7.2VMwareCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N
8.1NIST NVDCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesadmin
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-367Time-of-check Time-of-use (TOCTOU) Race Condition
T1005Data from Local System
T1565.001Stored Data Manipulation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo