Skip to main content
VulnerabilityPublished

CVE-2026-40968: Spring gRPC · Improper Isolation or Compartmentalization

Affects Spring gRPCSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 1.0.3 when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.0.3
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade Spring gRPC to 1.0.3.

Affected software

ProductAffectedFixed in
SpringSpring gRPCAffected
  • >=1.0.0 <1.0.3
Fixed in
  • 1.0.3
Mavenorg.lognet/spring-boot-grpc-starterpkg:maven/org.lognet/spring-boot-grpc-starterOther threatsAffected
  • =1.0.0
  • =1.0.1
  • =1.0.2
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Spring gRPC version 1.0.3. Users should upgrade to this version or later to remediate the vulnerability. Since no official vendor advisory or patch links are provided, verify the upgrade and patch status with the Spring project resources. Until upgraded, consider restricting access to affected versions and monitor for suspicious activity related to gRPC authentication contexts.

Description

When an authenticated user is denied access to a gRPC method, their authenticated identity remains bound to the gRPC worker thread and can be inherited by a subsequent unauthenticated request on the same thread. This may allow the subsequent user to gain escalated permissions. Affected versions: Spring gRPC: 1.0.0 - 1.0.2 (fixed in 1.0.3). Older, unsupported versions are also affected.

References

Community reviews

Loading reviews…