Is CVE-2026-40981 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-40981 being exploited in the wild.

How severe is CVE-2026-40981?

High severity, with a CVSS score of 7.5, published 7 May 2026.

Which products and versions are affected?

org.springframework.cloud:spring-cloud-config-server (Maven) ECOSYSTEM:introduced=3.1.0,last_affected=3.1.13; VMware Spring Cloud Config 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, 5.0.0 through 5.0.2.

Is there a fix for CVE-2026-40981?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-40981 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-40981?

Check whether you run org.springframework.cloud:spring-cloud-config-server (Maven) or VMware Spring Cloud Config at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-40981: VMware Spring Cloud Config auth bypass in Google Secrets Manager backend

CVE-2026-40981 · Severity: high · CVSS 7.5 · Published 2026-05-07

Spring Cloud Config is a service used to manage configuration settings and secrets for distributed applications. A security flaw exists when using Google Secrets Manager as a storage backend, which could allow an attacker to access sensitive information from Google Cloud projects they are not authorized to see. This could lead to the exposure of credentials, API keys, or other confidential data, potentially compromising the security of the entire cloud environment.

Technologies: org.springframework.cloud:spring-cloud-config-server (Maven), VMware Spring Cloud Config. Vendors: Maven, VMware.

Quick answers

Is CVE-2026-40981 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-40981 being exploited in the wild.
How severe is CVE-2026-40981?: High severity, with a CVSS score of 7.5, published 7 May 2026.
Which products and versions are affected?: org.springframework.cloud:spring-cloud-config-server (Maven) ECOSYSTEM:introduced=3.1.0,last_affected=3.1.13; VMware Spring Cloud Config 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, 5.0.0 through 5.0.2.
Is there a fix for CVE-2026-40981?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-40981 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-40981?: Check whether you run org.springframework.cloud:spring-cloud-config-server (Maven) or VMware Spring Cloud Config at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A vulnerability in Spring Cloud Config (CWE-639, CWE-1220) occurs when Google Secrets Manager is utilized as the backend storage. An unauthenticated remote attacker can craft malicious requests to the configuration server to bypass intended access controls. This allows for the unauthorized retrieval of secrets from GCP projects other than the one intended for the specific application context. The issue stems from insufficient granularity in access control and authorization bypass through user-controlled keys. Patches are available in versions 3.1.14, 4.1.10, 4.2.7, 4.3.3, and 5.0.3.

Affected products

VMware Spring Cloud Config 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, 5.0.0 through 5.0.2

Identifiers

CVE-2026-40981
GHSA-2mh5-3cw6-hrrq

Timeline

2026-05-07: disclosed
2026-05-07: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.