CVE-2026-41002
Last modified
CVE-2026-41002 is a high-severity vulnerability rated 8.1/10 on the CVSS scale. The base directory (`spring.cloud.config.server.git.basedir`) used by the Spring Cloud Config Server to clone Git repositories to is susceptible to time-of-check-time-of-use (TOCTOU) attacks. Spring Cloud Config 3.1.x: affected from 3.1.0 through 3.1.13 (inclusive); upgrade to 3.1.14 or greater (Enterprise Support Only). Spring Cloud Config 4.1.x: affected from 4.1.0 through 4.1.9 (inclusive); upgrade to 4.1.10 or greater (Enterprise Support Only). EPSS estimates a 0.22% chance of exploitation in the next 30 days.
Description
The base directory (`spring.cloud.config.server.git.basedir`) used by the Spring Cloud Config Server to clone Git repositories to is susceptible to time-of-check-time-of-use (TOCTOU) attacks. Spring Cloud Config 3.1.x: affected from 3.1.0 through 3.1.13 (inclusive); upgrade to 3.1.14 or greater (Enterprise Support Only). Spring Cloud Config 4.1.x: affected from 4.1.0 through 4.1.9 (inclusive); upgrade to 4.1.10 or greater (Enterprise Support Only). Spring Cloud Config 4.2.x: affected from 4.2.0 through 4.2.6 (inclusive); upgrade to 4.2.7 or greater (Enterprise Support Only). Spring Cloud Config 4.3.x: affected from 4.3.0 through 4.3.2 (inclusive); upgrade to 4.3.3 or greater. Spring Cloud Config 5.0.x: affected from 5.0.0 through 5.0.2 (inclusive); upgrade to 5.0.3 or greater.
Metrics
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Vmware | Spring Cloud Config | >= 3.1.0, < 3.1.14 |
| Vmware | Spring Cloud Config | >= 4.1.0, < 4.1.10 |
| Vmware | Spring Cloud Config | >= 4.2.0, < 4.2.7 |
| Vmware | Spring Cloud Config | >= 4.3.0, < 4.3.3 |
| Vmware | Spring Cloud Config | >= 5.0.0, < 5.0.3 |
References
- https://spring.io/security/cve-2026-41002Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-41002?
How severe is CVE-2026-41002?
How do I fix CVE-2026-41002?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-40997Several Spring WS integration paths with Spring Security cou…5.3
- CVE-2026-40998Jaxp13XPathTemplate evaluated XPath expressions for StreamSo…8.2
- CVE-2026-40999When WS-Addressing is used with non-anonymous ReplyTo or Fau…8.6
- CVE-2026-4100The Paid Memberships Pro plugin for WordPress is vulnerable …7.1
- CVE-2026-41000Wss4jSecurityInterceptor did not consistently wire Apache WS…3.7
- CVE-2026-41001Spring Boot's ArtemisEmbeddedConfigurationFactory uses a fix…5.3
- CVE-2026-41003An attacker able to influence values in RelyingPartyRegistra…5.4
- CVE-2026-41004When enabling trace logging in Spring Cloud Config Server se…4.4
- CVE-2026-41005Cloud Foundry UAA incorrectly treated XML encryption to the …9
- CVE-2026-41006Spring HATEOAS's internal PropertyUtils.createObjectFromProp…7.5
- CVE-2026-41007Spring HATEOAS maintains an unbounded static cache of String…7.5
- CVE-2026-41008Spring Security Authorization Server's authorization endpoin…6.1
Are you affected by CVE-2026-41002?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST