{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-81535 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-81535 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-81535 is a medium-severity missing authorization vulnerability in wolfSSL Inc. wolfSSH, published on 7 Oct 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-81535 and fix it if it is affected.\n\nWhat it is: CVE-2026-81535 is a medium-severity missing authorization vulnerability in wolfSSL Inc. wolfSSH, published on 7 Oct 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 CVE-2026-81535 in the wild and no public exploit code.\n\nAffected product: wolfSSL Inc. wolfSSH. 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-81535/ (Markdown: https://insights.sbomify.com/CVE-2026-81535/index.md)","id":"CVE-2026-81535","markdown":"https://insights.sbomify.com/CVE-2026-81535/index.md","name":"CVE-2026-81535","record":{"aliases":["GHSA-cqr9-f685-gr3w"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"wolfSSH library","requires_auth":"none","summary":"A malicious SSH peer can trigger unbounded memory allocation and unauthorized channel opens in wolfSSH clients built with forwarding enabled, causing denial of service.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"wolfSSL","cpe":[{"product":"wolfssh","vendor":"wolfssh"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"},{"id":"CWE-862","name":"Missing Authorization"}],"description":"In wolfSSH through 1.5.0 built with --enable-fwd, DoChannelOpen() in src/internal.c gates only direct-tcpip channel opens with the forwarding policy callback. forwarded-tcpip opens are admitted without an authorization check and are not capped in number, allowing a malicious SSH peer to make an endpoint allocate unbounded per-channel buffers for forwarding channels the application never authorized. A client also does not check a forwarded-tcpip open against the forwards it registered with a tcpip-forward request, as RFC 4254 section 7.2 requires, so a malicious server can open forwarding channels for addresses and ports the client never asked it to forward.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"wolfSSH SSH client accepts unsolicited forwarded-tcpip channel opens without an authorization check","id":"CVE-2026-81535","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"DataStage on Cloud Pak for Data has several vulnerabilities","id":"CVE-2026-81536"},"packages":[],"prev":{"headline":"Code injection in Email Customizer for WooCommerce (Pro)","id":"CVE-2026-81534"},"products":["wolfSSH"],"published":"2026-10-07","related":[{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2022-32073","kev_date_added":null,"published":"2022-07-13"},{"cvss_score":9.4,"headline":"Authentication Bypass","id":"CVE-2025-14942","kev_date_added":null,"published":"2026-01-06"},{"cvss_score":9.4,"headline":"Host verification bypass and credential leak","id":"CVE-2025-11625","kev_date_added":null,"published":"2025-10-21"},{"cvss_score":9.1,"headline":"User authentication bypass in wolfSSH server","id":"CVE-2024-2873","kev_date_added":null,"published":"2024-03-25"},{"cvss_score":9,"headline":"wolfSSH ECDSA host key curve not validated against negotiated algorithm","id":"CVE-2026-16516","kev_date_added":null,"published":"2026-10-07"},{"cvss_score":7.7,"headline":"wolfSSHd on Windows race condition leading to logon token reused across connections","id":"CVE-2026-83540","kev_date_added":null,"published":"2026-10-07"},{"cvss_score":6.9,"headline":"Denial of service in wolfSSH","id":"CVE-2026-84897","kev_date_added":null,"published":"2026-10-07"}],"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-10-07","vendors":["wolfSSL Inc."]},"summary":"A malicious SSH peer can trigger unbounded memory allocation and unauthorized channel opens in wolfSSH clients built with forwarding enabled, causing denial of service.","url":"https://insights.sbomify.com/CVE-2026-81535/"}