{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-40614 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-40614 is a high-severity memory corruption vulnerability in pjsip pjproject, published on 21 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-40614 and fix it if it is affected.\n\nWhat it is: CVE-2026-40614 is a high-severity memory corruption vulnerability in pjsip pjproject, published on 21 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-40614 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-40614/ (Markdown: https://insights.sbomify.com/CVE-2026-40614/index.md)","id":"CVE-2026-40614","markdown":"https://insights.sbomify.com/CVE-2026-40614/index.md","name":"CVE-2026-40614","record":{"aliases":["ALPINE-CVE-2026-40614","DEBIAN-CVE-2026-40614","GHSA-j59p-4xrr-fp8g","UBUNTU-CVE-2026-40614"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"PJSIP multimedia library","requires_auth":"none","summary":"A heap buffer overflow in PJSIP's Opus codec allows attackers to execute arbitrary code or cause denial of service via crafted audio frames.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"pjsip","vendor":"pjsip"}],"cvss":{"score":8.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"PJSIP is a free and open source multimedia communication library written in C. In 2.16 and earlier, there is a buffer overflow when decoding Opus audio frames due to insufficient buffer size validation in the Opus codec decode path. The FEC decode buffers (dec_frame[].buf) were allocated based on a PCM-derived formula: (sample_rate/1000) * 60 * channel_cnt * 2. At 8 kHz mono this yields only 960 bytes, but codec_parse() can output encoded frames up to MAX_ENCODED_PACKET_SIZE (1280) bytes via opus_repacketizer_out_range(). The three pj_memcpy() calls in codec_decode() copied input-\u003esize bytes without bounds checking, causing a heap buffer overflow.","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: Heap buffer overflow in Opus codec decoding","id":"CVE-2026-40614","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":"A stack-based buffer overflow vulnerability exists in the boa formParentControl deviceName functionality of X2000R (version(s): TOTOLINK-X20","id":"CVE-2026-40615"},"packages":[],"prev":{"headline":"Coturn: Misaligned Memory Access in coturn STUN Attribute Parser (Remote DoS on ARM64)","id":"CVE-2026-40613"},"products":["pjproject"],"published":"2026-04-21","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.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":"total"},"state":"PUBLISHED","updated":"2026-04-22","vendors":["pjsip"]},"summary":"A heap buffer overflow in PJSIP's Opus codec allows attackers to execute arbitrary code or cause denial of service via crafted audio frames.","url":"https://insights.sbomify.com/CVE-2026-40614/"}