{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-33069 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-33069 is a medium-severity memory corruption vulnerability in pjsip pjproject, published on 20 Mar 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-33069 and fix it if it is affected.\n\nWhat it is: CVE-2026-33069 is a medium-severity memory corruption vulnerability in pjsip pjproject, published on 20 Mar 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-33069 in the wild and no public exploit code.\n\nAffected product: pjsip pjproject. 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-33069/ (Markdown: https://insights.sbomify.com/CVE-2026-33069/index.md)","id":"CVE-2026-33069","markdown":"https://insights.sbomify.com/CVE-2026-33069/index.md","name":"CVE-2026-33069","record":{"aliases":["ALPINE-CVE-2026-33069","DEBIAN-CVE-2026-33069","GHSA-x5pq-qrp4-fmrj","UBUNTU-CVE-2026-33069"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"SIP multimedia library","requires_auth":"none","summary":"An out-of-bounds heap read in PJSIP allows attackers to read adjacent memory when processing SIP multipart messages, potentially disclosing sensitive data.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"pjsip","vendor":"pjsip"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"PJSIP is a free and open source multimedia communication library written in C. Versions 2.16 and below have a cascading out-of-bounds heap read in pjsip_multipart_parse(). After boundary string matching, curptr is advanced past the delimiter without verifying it has not reached the buffer end. This allows 1-2 bytes of adjacent heap memory to be read. All applications that process incoming SIP messages with multipart bodies or SDP content are potentially affected. This issue is resolved in version 2.17.","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":"PJSIP has an Out-of-bounds Read in SIP multipart parsing","id":"CVE-2026-33069","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"FileRise has Unauthenticated Share Link Deletion","id":"CVE-2026-33070"},"packages":[],"prev":{"headline":"Claude Code has a Workspace Trust Dialog Bypass via Repo-Controlled Settings File","id":"CVE-2026-33068"},"products":["pjproject"],"published":"2026-03-20","related":[{"cvss_score":8.7,"headline":"PJSIP: Heap use-after-free in PJSIP presence subscription termination handler","id":"CVE-2026-28799","kev_date_added":null,"published":"2026-03-06"},{"cvss_score":8.7,"headline":"PJSIP: Stack buffer overflow in Opus codec parser","id":"CVE-2026-29068","kev_date_added":null,"published":"2026-03-06"},{"cvss_score":8.5,"headline":"PJSIP: Heap buffer overflow in Opus codec decoding","id":"CVE-2026-40614","kev_date_added":null,"published":"2026-04-21"},{"cvss_score":8.4,"headline":"PJSIP is vulnerable to Heap-based Buffer Overflow through DNS parser","id":"CVE-2026-32945","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":8.1,"headline":"PJSIP: Stack buffer overflow in pjsip_auth_create_digest2()","id":"CVE-2026-40892","kev_date_added":null,"published":"2026-04-21"},{"cvss_score":8.1,"headline":"PJSIP has a Heap-based Buffer Overflow vulnerability in its H.264 unpacketizer","id":"CVE-2026-26967","kev_date_added":null,"published":"2026-02-20"},{"cvss_score":8.1,"headline":"PJSIP has a heap buffer overflow in ICE with long username","id":"CVE-2026-25994","kev_date_added":null,"published":"2026-02-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-03-20","vendors":["pjsip"]},"summary":"An out-of-bounds heap read in PJSIP allows attackers to read adjacent memory when processing SIP multipart messages, potentially disclosing sensitive data.","url":"https://insights.sbomify.com/CVE-2026-33069/"}