What is CVE-2026-40969?

CVE-2026-40969 is a low-severity security vulnerability in org.springframework.grpc:spring-grpc (maven), affecting versions < 1.0.3. It is fixed in 1.0.3.

How severe is CVE-2026-40969?

CVE-2026-40969 has a CVSS score of 3.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.springframework.grpc:spring-grpc are affected by CVE-2026-40969?

org.springframework.grpc:spring-grpc (maven) versions < 1.0.3 is affected.

Is there a fix for CVE-2026-40969?

Yes. CVE-2026-40969 is fixed in 1.0.3. Upgrade to this version or later.

Is CVE-2026-40969 exploitable, and should I be worried?

Whether CVE-2026-40969 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-40969 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-40969 in org.springframework.grpc:spring-grpc | Intelligent Application Security

Q: How severe is CVE-2026-40969?

CVE-2026-40969 has a CVSS score of 3.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of org.springframework.grpc:spring-grpc are affected by CVE-2026-40969?

org.springframework.grpc:spring-grpc (maven) versions < 1.0.3 is affected.

Q: Is there a fix for CVE-2026-40969?

Yes. CVE-2026-40969 is fixed in 1.0.3. Upgrade to this version or later.

Q: Is CVE-2026-40969 exploitable, and should I be worried?

Whether CVE-2026-40969 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-40969 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

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

Upgrade org.springframework.grpc:spring-grpc to 1.0.3 or later.

Summary

The raw message of every server-side AuthenticationException is returned to the unauthenticated remote caller in the gRPC status description. This allows an attacker to obtain information about the authentication failure, which may be useful for further attacks.

Affected versions:
Spring gRPC: 1.0.0 - 1.0.2 (fixed in 1.0.3). Older, unsupported versions are also affected.

Impact

CVE-2026-40969 has a CVSS score of 3.7 (Low). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.0.3); upgrading removes the vulnerable code path.

Affected versions

org.springframework.grpc:spring-grpc (< 1.0.3)

Security releases

org.springframework.grpc:spring-grpc → 1.0.3 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade org.springframework.grpc:spring-grpc to 1.0.3 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-40969? CVE-2026-40969 is a low-severity security vulnerability in org.springframework.grpc:spring-grpc (maven), affecting versions < 1.0.3. It is fixed in 1.0.3.
How severe is CVE-2026-40969? CVE-2026-40969 has a CVSS score of 3.7 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of org.springframework.grpc:spring-grpc are affected by CVE-2026-40969? org.springframework.grpc:spring-grpc (maven) versions < 1.0.3 is affected.
Is there a fix for CVE-2026-40969? Yes. CVE-2026-40969 is fixed in 1.0.3. Upgrade to this version or later.
Is CVE-2026-40969 exploitable, and should I be worried? Whether CVE-2026-40969 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-40969 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-40969? Upgrade org.springframework.grpc:spring-grpc to 1.0.3 or later.

Other vulnerabilities in org.springframework.grpc:spring-grpc

CVE-2026-40969