{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-49423 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-49423 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-49423 is a low-severity vulnerability in Freebsd Freebsd, published on 19 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-49423 and fix it if it is affected.\n\nWhat it is: CVE-2026-49423 is a low-severity vulnerability in Freebsd Freebsd, published on 19 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-49423 in the wild and no public exploit code.\n\nAffected product: Freebsd Freebsd. 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-49423/ (Markdown: https://insights.sbomify.com/CVE-2026-49423/index.md)","id":"CVE-2026-49423","markdown":"https://insights.sbomify.com/CVE-2026-49423/index.md","name":"CVE-2026-49423","record":{"aliases":["GHSA-c5hg-f3pf-qgxh"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"FreeBSD kernel","requires_auth":"low_privilege","summary":"A remote attacker can cause a kernel panic in FreeBSD by triggering uninitialized memory access during TLS record processing.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"freebsd","cpe":[{"product":"freebsd","vendor":"freebsd"}],"cvss":{"score":3.3,"severity":"low","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-908","name":"Use of Uninitialized Resource"}],"description":"When building the iovec array for a received TLS 1.2 CBC record, ktls_ocf_tls_cbc_decrypt() incremented the iovec index for every mbuf in the chain, including mbufs that were skipped because they contained only TLS header bytes.  This left uninitialized entries in the iovec array.  The iovec array was allocated without zeroing.\n\nA remote TLS peer can cause the kernel to read from uninitialized iovec entries during HMAC computation, resulting in a kernel panic.  The peer must be able to control TCP segmentation such that the first mbuf of a CBC record contains only the 5-byte TLS record header.","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":"Remote DOS via uninitialized memory access in KTLS receive","id":"CVE-2026-49423","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"freebsd:freebsd","products":["freebsd:freebsd"],"type":"null_dereference","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Kernel stack disclosure in Linux compatibility layer","id":"CVE-2026-49424"},"packages":[],"prev":{"headline":"Use-after-free in TCP RACK stack option handler","id":"CVE-2026-49422"},"products":["FreeBSD"],"published":"2026-08-19","related":[{"cvss_score":10,"headline":"Memory corruption in FreeBSD","id":"CVE-2018-17160","kev_date_added":null,"published":"2018-12-04"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2014-3954","kev_date_added":null,"published":"2014-10-27"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2006-4304","kev_date_added":null,"published":"2006-08-24"},{"cvss_score":10,"headline":"Integer overflow in n/a","id":"CVE-2006-0226","kev_date_added":null,"published":"2006-01-19"},{"cvss_score":10,"headline":"Denial of service in n/a","id":"CVE-2004-0002","kev_date_added":null,"published":"2004-02-03"},{"cvss_score":10,"headline":"Security feature bypass in n/a","id":"CVE-2001-0969","kev_date_added":null,"published":"2002-03-09"},{"cvss_score":10,"headline":"Denial of service in n/a","id":"CVE-2001-0388","kev_date_added":null,"published":"2001-09-18"}],"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-08-26","vendors":["FreeBSD"]},"summary":"A remote attacker can cause a kernel panic in FreeBSD by triggering uninitialized memory access during TLS record processing.","url":"https://insights.sbomify.com/CVE-2026-49423/"}