{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-46806 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2025-46806 is a medium-severity vulnerability in https://github.com/yrutschle/sslh/releases/tag/v2.2.4 sslh, published on 2 Jun 2025."},"fix_prompt":"Check this codebase for CVE-2025-46806 and fix it if it is affected.\n\nWhat it is: CVE-2025-46806 is a medium-severity vulnerability in https://github.com/yrutschle/sslh/releases/tag/v2.2.4 sslh, published on 2 Jun 2025. \nExploitation: There is no known exploitation of CVE-2025-46806 in the wild and no public exploit code.\n\nAffected product: https://github.com/yrutschle/sslh/releases/tag/v2.2.4 sslh. 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-2025-46806/ (Markdown: https://insights.sbomify.com/CVE-2025-46806/index.md)","id":"CVE-2025-46806","markdown":"https://insights.sbomify.com/CVE-2025-46806/index.md","name":"CVE-2025-46806","record":{"aliases":["DEBIAN-CVE-2025-46806","GHSA-9pc8-3wwf-wg5j","UBUNTU-CVE-2025-46806"],"analysis":null,"analysis_generated_by":null,"assigner":"suse","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-823","name":"Use of Out-of-range Pointer Offset"}],"description":"A Use of Out-of-range Pointer Offset vulnerability in sslh leads to denial of service on some architectures.This issue affects sslh before 2.2.4.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Misaligned Memory Accesses in `is_openvpn_protocol()`","id":"CVE-2025-46806","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"File Descriptor Exhaustion in sslh-select and sslh-ev triggers SEGFAULT","id":"CVE-2025-46807"},"packages":[],"prev":{"headline":"Screen version 5.0.0 and older version 4 releases have a TOCTOU race potentially allowing to send SIGHUP, SIGCONT to privileged processes wh","id":"CVE-2025-46805"},"products":["sslh"],"published":"2025-06-02","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-02","vendors":["https://github.com/yrutschle/sslh/releases/tag/v2.2.4"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2025-46806/"}