{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-25058 exists.","fix":"No fix has been published for CVE-2026-25058 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-25058 is a high-severity missing authorization 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-25058 and fix it if it is affected.\n\nWhat it is: CVE-2026-25058 is a high-severity missing authorization 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-25058 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-25058/ (Markdown: https://insights.sbomify.com/CVE-2026-25058/index.md)","id":"CVE-2026-25058","markdown":"https://insights.sbomify.com/CVE-2026-25058/index.md","name":"CVE-2026-25058","record":{"aliases":["GHSA-w73r-2449-qwgh"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Meeting transcription API","requires_auth":"none","summary":"Unauthenticated attackers can access internal transcript endpoints to steal confidential meeting data, passwords, and PII from Vexa deployments.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"vexa","vendor":"vexa"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"Vexa is an open-source, self-hostable meeting bot API and meeting transcription API. Prior to 0.10.0-260419-1910, the Vexa transcription-collector service exposes an internal endpoint `GET /internal/transcripts/{meeting_id}` that returns transcript data for any meeting without any authentication or authorization checks. An unauthenticated attacker can enumerate all meeting IDs, access any user's meeting transcripts without credentials, and steal confidential business conversations, passwords, and/or PII. 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's unauthenticated internal transcript endpoint exposed by default","id":"CVE-2026-25058","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"OpenList affected by Path Traversal in file copy and remove handlers","id":"CVE-2026-25059"},"packages":[],"prev":{"headline":"Zip Slip in MarkUs config upload allowing RCE","id":"CVE-2026-25057"},"products":["vexa"],"published":"2026-04-20","related":[{"cvss_score":5.8,"headline":"Vexa Webhook Feature has a SSRF Vulnerability","id":"CVE-2026-25883","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":"Unauthenticated attackers can access internal transcript endpoints to steal confidential meeting data, passwords, and PII from Vexa deployments.","url":"https://insights.sbomify.com/CVE-2026-25058/"}