{"answers":{"affected":"","exploited":"There is no known exploitation of openSUSE-SU-2026:20589-1 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"openSUSE-SU-2026:20589-1 is a memory corruption vulnerability in tor, 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 openSUSE-SU-2026:20589-1 and fix it if it is affected.\n\nWhat it is: openSUSE-SU-2026:20589-1 is a memory corruption vulnerability in tor, published on 20 Apr 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 openSUSE-SU-2026:20589-1 in the wild and no public exploit code.\n\nAffected product: tor. 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/openSUSE-SU-2026-20589-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2026-20589-1/index.md)","id":"openSUSE-SU-2026:20589-1","markdown":"https://insights.sbomify.com/openSUSE-SU-2026-20589-1/index.md","name":"openSUSE-SU-2026:20589-1","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Tor anonymity network","requires_auth":"none","summary":"Remote attackers can cause a denial of service via memory corruption flaws in the Tor network software, requiring an upgrade to the latest version.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"This update for tor fixes the following issues:\n\nChanges in tor:\n\n- update to 0.4.8.23:\n  * Fix a memory compare using the wrong length. This could lead to\n    a remote crash when using the conflux subsystem\n    (TROVE-2026-004, boo#1262302)\n  * Fix a series of defense in depth security issues found across\n    the codebase\n  * Regenerate fallback directories generated on March 25, 2026.\n  * Update the geoip files to match the IPFire Location Database,\n    as retrieved on 2026/03/25.\n- includes changes from 0.4.8.22:\n  * Avoid an out-of-bounds read error that could occur with\n    V1-formatted EXTEND cells\n    (TROVE-2025-016, boo#1262301)\n  * Allow old clients to fetch the consensus even if they use\n    version 0 of the SENDME protocol\n  * Do not check for compression bombs for buffers smaller than\n    5MB (increased from 64 KB)\n  * Improvements to directory server statistics\n\n- update to 0.4.8.21:\n  * This release is a continuation of the previous one and\n    addresses additional Conflux-related issues identified through\n    further testing and feedback from relay operators. We strongly\n    recommend upgrading as soon as possible.\n  * Major bugfixes (conflux, exit):\n    - When dequeuing out-of-order conflux cells, the circuit\n    could be close in between two dequeue which could lead to a\n    mishandling of a NULL pointer. Fixes bug 41162;\n  * Add -mbranch-protection=standard for arm64.\n  * Regenerate fallback directories generated on November\n  * Update the geoip files to match the IPFire Location\n    Database, as retrieved on 2025/11/17.\n  * Fix a bug causing the initial tor process to hang\n    intead of exiting with RunAsDaemon, when pluggable transports\n    are used.\n\n- 0.4.8.20\n  * Add a new hardening compiler flag -fcf-protection=full\n  * Fix the root cause of some conflux fragile asserts\n  * Fix a series of conflux edge cases\n\n- 0.4.8.19\n  * Fix some clients not being able to connect to LibreSSL relays\n  * Improve stream flow control performance","ecosystems":["openSUSE:Leap 16.0"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Security update for tor","id":"openSUSE-SU-2026:20589-1","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"openSUSE:Leap 16.0","fixed":["0.4.8.23-bp160.1.1"],"introduced":["0"],"last_affected":[],"package":"tor","purl":"pkg:rpm/opensuse/tor\u0026distro=openSUSE%20Leap%2016.0","source":"openSUSE-SU-2026:20589-1"}],"products":null,"published":"2026-04-20","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Remote attackers can cause a denial of service via memory corruption flaws in the Tor network software, requiring an upgrade to the latest version.","url":"https://insights.sbomify.com/openSUSE-SU-2026-20589-1/"}