{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2026-5926 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-5926 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-5926 is a medium-severity vulnerability in Ibm Security Verify Access, published on 22 Apr 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-5926 and fix it if it is affected.\n\nWhat it is: CVE-2026-5926 is a medium-severity vulnerability in Ibm Security Verify Access, published on 22 Apr 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-5926 in the wild and no public exploit code.\n\nAffected product: Ibm Security Verify Access. 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-5926/ (Markdown: https://insights.sbomify.com/CVE-2026-5926/index.md)","id":"CVE-2026-5926","markdown":"https://insights.sbomify.com/CVE-2026-5926/index.md","name":"CVE-2026-5926","record":{"aliases":["GHSA-5rff-j8g7-m3r3"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"IBM Verify Access","requires_auth":"low_privilege","summary":"Weak cryptographic algorithms in IBM Verify Access allow attackers to decrypt highly sensitive information.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ibm","cpe":[{"product":"security_verify_access","vendor":"ibm"},{"product":"security_verify_access_container","vendor":"ibm"},{"product":"verify_identity_access","vendor":"ibm"},{"product":"verify_identity_access_container","vendor":"ibm"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"IBM Verify Identity Access Container 11.0 through 11.0.2 and IBM Security Verify Access Container 10.0 through 10.0.9.1 and IBM Verify Identity Access 11.0 through 11.0.2 and IBM Security Verify Access 10.0 through 10.0.9.1 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information.","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":"Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access","id":"CVE-2026-5926","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"ibm:security_verify_access","products":["ibm:security_verify_access"],"type":"weak_cryptography","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Potential buffer under-read in ungetwc","id":"CVE-2026-5928"},"packages":[],"prev":{"headline":"Getwid \u003c= 2.1.3 - Authenticated (Contributor+) Stored Cross-Site Scripting via Google Maps 'customStyle'","id":"CVE-2026-5924"},"products":["Security Verify Access","Security Verify Access Container","Verify Identity Access","Verify Identity Access Container"],"published":"2026-04-22","related":[{"cvss_score":9.8,"headline":"Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access","id":"CVE-2026-78401","kev_date_added":null,"published":"2026-10-08"},{"cvss_score":9.8,"headline":"Security vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access","id":"CVE-2026-78406","kev_date_added":null,"published":"2026-10-08"},{"cvss_score":9.8,"headline":"IBM Security Verify Access Appliance command execution","id":"CVE-2024-49803","kev_date_added":null,"published":"2024-11-29"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2021-39070","kev_date_added":null,"published":"2022-02-02"},{"cvss_score":9.4,"headline":"IBM Security Verify Access Appliance hard coded credentials","id":"CVE-2024-49805","kev_date_added":null,"published":"2024-11-29"},{"cvss_score":9.4,"headline":"IBM Security Verify Access Appliance hard coded credentials","id":"CVE-2024-49806","kev_date_added":null,"published":"2024-11-29"},{"cvss_score":9.3,"headline":"Security Vulnerabilities have been found in IBM Verify Identity Access and IBM Security Verify Access","id":"CVE-2026-1346","kev_date_added":null,"published":"2026-04-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":"partial"},"state":"PUBLISHED","updated":"2026-04-23","vendors":["IBM"]},"summary":"Weak cryptographic algorithms in IBM Verify Access allow attackers to decrypt highly sensitive information.","url":"https://insights.sbomify.com/CVE-2026-5926/"}