{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-64630 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-64630 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-64630 is a medium-severity missing authorization vulnerability in Veeam ONE, published on 4 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-64630 and fix it if it is affected.\n\nWhat it is: CVE-2026-64630 is a medium-severity missing authorization vulnerability in Veeam ONE, published on 4 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-64630 in the wild and no public exploit code.\n\nAffected product: Veeam ONE. 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-64630/ (Markdown: https://insights.sbomify.com/CVE-2026-64630/index.md)","id":"CVE-2026-64630","markdown":"https://insights.sbomify.com/CVE-2026-64630/index.md","name":"CVE-2026-64630","record":{"aliases":["GHSA-685g-v9jx-pxqq"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Veeam ONE","requires_auth":"low_privilege","summary":"A low-privileged user can access report data outside the scope of a shared report link in Veeam ONE.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"A vulnerability allowing a low-privileged user to retrieve report data outside the scope of a shared report link.","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":"Missing authorization in ONE","id":"CVE-2026-64630","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":"SQL injection in ONE","id":"CVE-2026-64631"},"packages":[],"prev":{"headline":"Memory corruption in Parasolid V38.0","id":"CVE-2026-64629"},"products":["ONE"],"published":"2026-08-04","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-08-04","vendors":["Veeam"]},"summary":"A low-privileged user can access report data outside the scope of a shared report link in Veeam ONE.","url":"https://insights.sbomify.com/CVE-2026-64630/"}