{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-110912 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-110912 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-110912 is a high-severity vulnerability in DragonFlyBSD, published on 15 Oct 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-110912 and fix it if it is affected.\n\nWhat it is: CVE-2026-110912 is a high-severity vulnerability in DragonFlyBSD, published on 15 Oct 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-110912 in the wild and no public exploit code.\n\nAffected product: DragonFlyBSD. 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-110912/ (Markdown: https://insights.sbomify.com/CVE-2026-110912/index.md)","id":"CVE-2026-110912","markdown":"https://insights.sbomify.com/CVE-2026-110912/index.md","name":"CVE-2026-110912","record":{"aliases":["GHSA-r2jj-8gwv-75pj"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"DragonFly BSD kernel","requires_auth":"none","summary":"An unauthenticated attacker on the adjacent network can disclose kernel memory via crafted ARP packets in DragonFly BSD.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-130","name":"Improper Handling of Length Parameter Inconsistency"}],"description":"In DragonFly BSD through 6.4.2 before 4bb22ff, the ARP input handlers arpintr() and in_arpinput() (sys/netinet/if_ether.c) do not validate the hardware address length (ar_hln) and protocol address length (ar_pln) fields of incoming ARP packets. in_arpreply() then uses these attacker-controlled values as memcpy lengths when copying from kernel buffers that are only 6 and 4 bytes long, resulting in an out-of-bounds read of kernel heap and stack memory that is copied into the ARP reply sent back to the requester. An unauthenticated attacker on the adjacent network can use a single crafted ARP request to disclose up to roughly 250 bytes of each type of kernel memory, including kernel pointers. This is expected to be fixed in the 6.6 stable release when that is available.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-10-15","github_poc":2,"max_poc_stars":2,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-10-15T15:21:35Z","kind":"github_poc","ref":"https://github.com/0xredash/CVE-2026-110912","stars":2,"title":"CVE-2026-110912"},{"date":"2026-10-15T07:43:45Z","kind":"github_poc","ref":"https://github.com/dreamfast/CVE-2026-110912","stars":0,"title":"A PoC for CVE-2026-110912 'arpbleed'"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Information disclosure in DragonFlyBSD","id":"CVE-2026-110912","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in Chrome","id":"CVE-2026-110913"},"packages":[],"prev":{"headline":"SQL injection in Wheels","id":"CVE-2026-110911"},"products":["DragonFlyBSD"],"published":"2026-10-15","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-10-16","vendors":["DragonFlyBSD"]},"summary":"An unauthenticated attacker on the adjacent network can disclose kernel memory via crafted ARP packets in DragonFly BSD.","url":"https://insights.sbomify.com/CVE-2026-110912/"}