{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-89162 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-89162 is a low-severity vulnerability in PCRE2, published on 11 Sep 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-89162 and fix it if it is affected.\n\nWhat it is: CVE-2026-89162 is a low-severity vulnerability in PCRE2, published on 11 Sep 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-89162 in the wild and no public exploit code.\n\nAffected product: PCRE2. 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-89162/ (Markdown: https://insights.sbomify.com/CVE-2026-89162/index.md)","id":"CVE-2026-89162","markdown":"https://insights.sbomify.com/CVE-2026-89162/index.md","name":"CVE-2026-89162","record":{"aliases":["ALPINE-CVE-2026-89162","BELL-CVE-2026-89162","DEBIAN-CVE-2026-89162","GHSA-mv4q-849q-vg78","GHSA-q7rw-r7qq-2hx6","MINI-r677-rvqh-gh27","UBUNTU-CVE-2026-89162"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"PCRE2 regex library","requires_auth":"none","summary":"An attacker with unsafe access can potentially read two bytes of memory via the pcre2_serialize_encode function in PCRE2.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"pcre2","vendor":"pcre"}],"cvss":{"score":2.9,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-669","name":"Incorrect Resource Transfer Between Spheres"}],"description":"In PCRE2 before 10.48, pcre2_serialize_encode might disclose two bytes to an adversary, typically in a situation where the access available to the adversary is already unsafe.","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":"Information disclosure in PCRE2","id":"CVE-2026-89162","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":"Security feature bypass in live-boot","id":"CVE-2026-89169"},"packages":[],"prev":{"headline":"Use after free in PCRE2","id":"CVE-2026-89161"},"products":["PCRE2"],"published":"2026-09-11","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-8786","kev_date_added":null,"published":"2017-05-05"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-8399","kev_date_added":null,"published":"2017-05-01"},{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2022-41409","kev_date_added":null,"published":"2023-07-18"},{"cvss_score":7.4,"headline":"Use after free in PCRE2","id":"CVE-2026-89161","kev_date_added":null,"published":"2026-09-11"},{"cvss_score":6.9,"headline":"PCRE2: heap-buffer-overflow read in match_ref due to missing boundary restoration in SCS","id":"CVE-2025-58050","kev_date_added":null,"published":"2025-08-27"},{"cvss_score":6.5,"headline":"Integer overflow in PCRE2","id":"CVE-2026-89158","kev_date_added":null,"published":"2026-09-11"},{"cvss_score":5.7,"headline":"Memory corruption in PCRE2","id":"CVE-2026-89157","kev_date_added":null,"published":"2026-09-11"}],"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-09-14","vendors":["PCRE"]},"summary":"An attacker with unsafe access can potentially read two bytes of memory via the pcre2_serialize_encode function in PCRE2.","url":"https://insights.sbomify.com/CVE-2026-89162/"}