{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25883 exists.","fix":"No fix has been published for CVE-2026-25883 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-25883 is a medium-severity server-side request forgery vulnerability in Vexa-ai vexa, published on 20 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-25883 and fix it if it is affected.\n\nWhat it is: CVE-2026-25883 is a medium-severity server-side request forgery vulnerability in Vexa-ai vexa, published on 20 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25883 exists.\n\nAffected product: Vexa-ai vexa. 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-25883/ (Markdown: https://insights.sbomify.com/CVE-2026-25883/index.md)","id":"CVE-2026-25883","markdown":"https://insights.sbomify.com/CVE-2026-25883/index.md","name":"CVE-2026-25883","record":{"aliases":["GHSA-fhr6-8hff-cvg4"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Meeting bot API","requires_auth":"none","summary":"Authenticated attackers can exploit unvalidated webhook URLs to access internal services and cloud metadata, risking credential theft and data exposure.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"vexa","vendor":"vexa"}],"cvss":{"score":5.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Vexa is an open-source, self-hostable meeting bot API and meeting transcription API. Prior to 0.10.0-260419-1910, the Vexa webhook feature allows authenticated users to configure an arbitrary URL that receives HTTP POST requests when meetings complete. The application performs no validation on the webhook URL, enabling Server-Side Request Forgery (SSRF). An authenticated attacker can set their webhook URL to target internal services (Redis, databases, admin panels), cloud metadata endpoints (AWS/GCP credential theft), and/or localhost services. Version 0.10.0-260419-1910 patches the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Vexa Webhook Feature has a SSRF Vulnerability","id":"CVE-2026-25883","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Exiv2: Out-of-bounds read in CrwMap::decode0x0805","id":"CVE-2026-25884"},"packages":[],"prev":{"headline":"Fiber has a Denial of Service Vulnerability via Route Parameter Overflow","id":"CVE-2026-25882"},"products":["vexa"],"published":"2026-04-20","related":[{"cvss_score":7.5,"headline":"Vexa's unauthenticated internal transcript endpoint exposed by default","id":"CVE-2026-25058","kev_date_added":null,"published":"2026-04-20"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-20","vendors":["Vexa-ai"]},"summary":"Authenticated attackers can exploit unvalidated webhook URLs to access internal services and cloud metadata, risking credential theft and data exposure.","url":"https://insights.sbomify.com/CVE-2026-25883/"}