CVE-2026-41002

Q: What is the severity of CVE-2026-41002?

CVE-2026-41002 has a medium severity rating due to its potential for exploitation through TOCTOU attacks.

Q: How do I fix CVE-2026-41002?

To fix CVE-2026-41002, upgrade your Spring Cloud Config Server to version 3.1.14 or greater.

Q: Which versions of Spring Cloud Config are affected by CVE-2026-41002?

CVE-2026-41002 affects Spring Cloud Config versions 3.1.0 to 3.1.13, 4.1.0 to 4.1.9, 4.2.0 to 4.2.6, 4.3.0 to 4.3.2, and 5.0.0 to 5.0.2.

Q: What type of attack is CVE-2026-41002 associated with?

CVE-2026-41002 is associated with time-of-check-time-of-use (TOCTOU) attacks.

Q: Is there a workaround for CVE-2026-41002?

No specific workaround is provided for CVE-2026-41002, so upgrading to a fixed version is recommended.

Published May 7, 2026

Updated

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.

Affected Software

6 affected components

Spring Spring Cloud Config>=3.1.0<=3.1.13, >=4.1.0<=4.1.9, >=4.2.0<=4.2.6, >=4.3.0<=4.3.2, >=5.0.0<=5.0.2

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

Event History

May 7, 2026

CVE Published

via MITRE·03:53 AM

Data Sourced

via MITRE·03:53 AM

DescriptionSeverityWeakness

Data Sourced

via NVD·04:16 AM

DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

What is the severity of CVE-2026-41002?

CVE-2026-41002 has a medium severity rating due to its potential for exploitation through TOCTOU attacks.

How do I fix CVE-2026-41002?

To fix CVE-2026-41002, upgrade your Spring Cloud Config Server to version 3.1.14 or greater.

Which versions of Spring Cloud Config are affected by CVE-2026-41002?

CVE-2026-41002 affects Spring Cloud Config versions 3.1.0 to 3.1.13, 4.1.0 to 4.1.9, 4.2.0 to 4.2.6, 4.3.0 to 4.3.2, and 5.0.0 to 5.0.2.

What type of attack is CVE-2026-41002 associated with?

CVE-2026-41002 is associated with time-of-check-time-of-use (TOCTOU) attacks.

Is there a workaround for CVE-2026-41002?

No specific workaround is provided for CVE-2026-41002, so upgrading to a fixed version is recommended.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.