{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-81829 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-81829 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-81829 is a medium-severity server-side request forgery vulnerability in Red Hat Exploit Intelligence, published on 17 Sep 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-81829 and fix it if it is affected.\n\nWhat it is: CVE-2026-81829 is a medium-severity server-side request forgery vulnerability in Red Hat Exploit Intelligence, published on 17 Sep 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-81829 in the wild and no public exploit code.\n\nAffected product: Red Hat Exploit Intelligence. 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-81829/ (Markdown: https://insights.sbomify.com/CVE-2026-81829/index.md)","id":"CVE-2026-81829","markdown":"https://insights.sbomify.com/CVE-2026-81829/index.md","name":"CVE-2026-81829","record":{"aliases":["GHSA-66cv-5wq4-p78m"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"SmallRye JWT library","requires_auth":"none","summary":"Unauthenticated attackers can force server-side requests to arbitrary same-origin paths via unsanitized JWT kid headers, potentially exposing internal data.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"A flaw was found in SmallRye JWT's AwsAlbKeyResolver, which is used by applications to verify JSON Web Tokens signed by AWS Application Load Balancers. When the AWS_ALB key provider is configured, the resolver constructs the key-fetch URL by directly concatenating the attacker-controlled kid header value from an inbound JWT without sanitizing path traversal characters or query-string separators. This allows an unauthenticated remote attacker to force the application server to issue GET requests to arbitrary paths on the same origin as the configured key endpoint. As a result, non-public endpoints or internal data reachable on that origin may be read by the attacker before JWT signature verification takes place.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Server-side request forgery in Exploit Intelligence","id":"CVE-2026-81829","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Path traversal in OpenVPN","id":"CVE-2026-81830"},"packages":[],"prev":{"headline":"Flowintel Login Email Validation Bypass Allows Log Injection via Crafted Email Input","id":"CVE-2026-81827"},"products":["Exploit Intelligence","Red Hat JBoss Enterprise Application Platform 8","Red Hat JBoss Enterprise Application Platform Expansion Pack","Red Hat build of Apicurio Registry 3","Red Hat build of Quarkus","Red Hat build of Quarkus 3.27.5.SP2","Red Hat build of Quarkus 3.33.3.SP2"],"published":"2026-09-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-09","vendors":["Red Hat"]},"summary":"Unauthenticated attackers can force server-side requests to arbitrary same-origin paths via unsanitized JWT kid headers, potentially exposing internal data.","url":"https://insights.sbomify.com/CVE-2026-81829/"}