{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-47879 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-47879 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-47879 is a high-severity server-side request forgery vulnerability in Spring Cloud Gateway, published on 27 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-47879 and fix it if it is affected.\n\nWhat it is: CVE-2026-47879 is a high-severity server-side request forgery vulnerability in Spring Cloud Gateway, published on 27 Aug 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-47879 in the wild and no public exploit code.\n\nAffected product: Spring Cloud Gateway. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-47879/ (Markdown: https://insights.sbomify.com/CVE-2026-47879/index.md)","id":"CVE-2026-47879","markdown":"https://insights.sbomify.com/CVE-2026-47879/index.md","name":"CVE-2026-47879","record":{"aliases":["GHSA-7mwm-q6x4-5h32"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Spring Cloud Gateway","requires_auth":"high_privilege","summary":"Attackers can exploit arbitrary Spring Resource locations in gRPC filters to perform Server-Side Request Forgery and access native files.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"vmware","cpe":[{"product":"spring_cloud_gateway","vendor":"vmware"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Spring Cloud Gateway JsonToGrpcGatewayFilterFactory allows arbitrary Spring Resource locations for defining the proto descriptor.\nSpring Cloud Gateway 5.0.0 - 5.0.2\nSpring Cloud Gateway 4.3.0 - 4.3.5\nSpring Cloud Gateway 4.0.0 - 4.2.9\nSpring Cloud Gateway 3.1.13 and earlier","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Spring Cloud Gateway SSRF and native file access with gRPC","id":"CVE-2026-47879","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"DefaultJmsHeaderMapper copies all JMS user properties into MessageHeaders without excluding framework-significant names","id":"CVE-2026-47880"},"packages":[],"prev":{"headline":"Unsafe Java deserialization in DefaultExecutionContextSerializer without class allowlist","id":"CVE-2026-47878"},"products":["Spring Cloud Gateway"],"published":"2026-08-27","related":[{"cvss_score":8.6,"headline":"Spring Cloud Gateway Server Forwards Headers from Untrusted Proxies in certain situations","id":"CVE-2026-47825","kev_date_added":null,"published":"2026-06-15"},{"cvss_score":7.5,"headline":"SSL bundle configuration silently bypassed in Spring Cloud Gateway","id":"CVE-2026-22750","kev_date_added":null,"published":"2026-04-10"},{"cvss_score":6.5,"headline":"Request injection in Spring Cloud Gateway","id":"CVE-2021-22051","kev_date_added":null,"published":"2021-11-08"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2026-08-27","vendors":["Spring"]},"summary":"Attackers can exploit arbitrary Spring Resource locations in gRPC filters to perform Server-Side Request Forgery and access native files.","url":"https://insights.sbomify.com/CVE-2026-47879/"}