Skip to content

← Public intelligence

Maven package

org.springframework.grpc:spring-grpc

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Low, CVSS 3.7MavenPublished

    Spring gRPC AuthenticationException messages are reflected to remote client

    CVE-2026-40969 · GHSA-37w2-q6vh-45v6

    Affected
    • Maven org.springframework.grpc:spring-grpc < 1.0.3
    Fixed in
    1.0.3· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 1.0.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 4.2MavenPublished

    Spring gRPC SecurityContext leaks across requests upon authorization failure

    CVE-2026-40968 · GHSA-4g9c-3x4p-mfpp

    Affected
    • Maven org.springframework.grpc:spring-grpc < 1.0.3
    Fixed in
    1.0.3· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 1.0.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →