{"answers":{"affected":"2 open source packages ship an affected version, including org.springframework.grpc:spring-grpc. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-40969 in the wild and no public exploit code.","fix":"Upgrade org.springframework.grpc:spring-grpc to 1.0.3 or later.","what":"CVE-2026-40969 is a low-severity vulnerability in Spring gRPC, published on 28 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-40969 and fix it if it is affected.\n\nWhat it is: CVE-2026-40969 is a low-severity vulnerability in Spring gRPC, published on 28 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-40969 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.springframework.grpc:spring-grpc (Maven): affected all versions; fixed in 1.0.3\n- org.springframework.grpc:spring-grpc (Maven): affected all versions; fixed in 1.0.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-40969/ (Markdown: https://insights.sbomify.com/CVE-2026-40969/index.md)","id":"CVE-2026-40969","markdown":"https://insights.sbomify.com/CVE-2026-40969/index.md","name":"CVE-2026-40969","record":{"aliases":["GHSA-37w2-q6vh-45v6"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Spring gRPC library","requires_auth":"none","summary":"An attacker can obtain sensitive authentication failure details from gRPC status descriptions, aiding further attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[{"product":"spring_grpc","vendor":"vmware"}],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-209","name":"Generation of Error Message Containing Sensitive Information"}],"description":"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.\n\nAffected versions:\nSpring gRPC: 1.0.0 - 1.0.2 (fixed in 1.0.3). Older, unsupported versions are also affected.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Spring gRPC AuthenticationException message reflected to remote client","id":"CVE-2026-40969","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Spring Boot's Elasticsearch auto-configuration doesn't perform hostname verification when connecting to the Elasticsearch server.","id":"CVE-2026-40970"},"packages":[{"ecosystem":"Maven","fixed":["1.0.3"],"introduced":["0"],"last_affected":[],"package":"org.springframework.grpc:spring-grpc","purl":null,"source":"GHSA-37w2-q6vh-45v6"},{"ecosystem":"Maven","fixed":["1.0.3"],"introduced":["0"],"last_affected":[],"package":"org.springframework.grpc:spring-grpc","purl":"pkg:maven/org.springframework.grpc/spring-grpc","source":"GHSA-37w2-q6vh-45v6"}],"prev":{"headline":"Spring gRPC SecurityContext leaks across requests on authorization failure","id":"CVE-2026-40968"},"products":["Spring gRPC"],"published":"2026-04-28","related":[{"cvss_score":4.3,"headline":"Spring gRPC SecurityContext leaks across requests on authorization failure","id":"CVE-2026-40968","kev_date_added":null,"published":"2026-04-28"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-28","vendors":["Spring"]},"summary":"An attacker can obtain sensitive authentication failure details from gRPC status descriptions, aiding further attacks.","url":"https://insights.sbomify.com/CVE-2026-40969/"}