{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-67269 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2025-67269 is a high-severity vulnerability in n/a, published on 2 Jan 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-2025-67269 and fix it if it is affected.\n\nWhat it is: CVE-2025-67269 is a high-severity vulnerability in n/a, published on 2 Jan 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-2025-67269 in the wild and no public exploit code.\n\nAffected product: n/a. 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-67269/ (Markdown: https://insights.sbomify.com/CVE-2025-67269/index.md)","id":"CVE-2025-67269","markdown":"https://insights.sbomify.com/CVE-2025-67269/index.md","name":"CVE-2025-67269","record":{"aliases":["DEBIAN-CVE-2025-67269","GHSA-xcj3-m9c5-2prq","OESA-2026-3035","UBUNTU-CVE-2025-67269"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"GPS daemon","requires_auth":"none","summary":"An integer underflow in gpsd allows attackers to cause a denial of service via high CPU utilization when parsing malformed NAVCOM packets.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gpsd","vendor":"gpsd_project"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-191","name":"Integer Underflow (Wrap or Wraparound)"}],"description":"An integer underflow vulnerability exists in the `nextstate()` function in `gpsd/packet.c` of gpsd versions prior to commit `ffa1d6f40bca0b035fc7f5e563160ebb67199da7`. When parsing a NAVCOM packet, the payload length is calculated using `lexer-\u003elength = (size_t)c - 4` without checking if the input byte `c` is less than 4. This results in an unsigned integer underflow, setting `lexer-\u003elength` to a very large value (near `SIZE_MAX`). The parser then enters a loop attempting to consume this massive number of bytes, causing 100% CPU utilization and a Denial of Service (DoS) condition.","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":"Integer overflow in n/a","id":"CVE-2025-67269","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in n/a","id":"CVE-2025-67274"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2025-67268"},"products":["n/a"],"published":"2026-01-02","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2025-67268","kev_date_added":null,"published":"2026-01-02"},{"cvss_score":8.4,"headline":"gpsd gpsprof Command Injection via gnuplot plot title subtype field","id":"CVE-2026-58459","kev_date_added":null,"published":"2026-07-09"},{"cvss_score":5.9,"headline":"Integer overflow in GPSd","id":"CVE-2023-43628","kev_date_added":null,"published":"2023-12-05"}],"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-15","vendors":["n/a"]},"summary":"An integer underflow in gpsd allows attackers to cause a denial of service via high CPU utilization when parsing malformed NAVCOM packets.","url":"https://insights.sbomify.com/CVE-2025-67269/"}