{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-34876 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-34876 is a high-severity vulnerability in n/a, published on 2 Apr 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-34876 and fix it if it is affected.\n\nWhat it is: CVE-2026-34876 is a high-severity vulnerability in n/a, published on 2 Apr 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-34876 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-2026-34876/ (Markdown: https://insights.sbomify.com/CVE-2026-34876/index.md)","id":"CVE-2026-34876","markdown":"https://insights.sbomify.com/CVE-2026-34876/index.md","name":"CVE-2026-34876","record":{"aliases":["DEBIAN-CVE-2026-34876","ECHO-2b14-d1fe-8a7a","GHSA-jw9g-6hxw-4whq","UBUNTU-CVE-2026-34876"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Mbed TLS library","requires_auth":"none","summary":"Attackers can read adjacent memory via oversized tag_len in Mbed TLS CCM API, potentially exposing sensitive context data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mbed_tls","vendor":"trustedfirmware"}],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"An issue was discovered in Mbed TLS 3.x before 3.6.6. An out-of-bounds read vulnerability in mbedtls_ccm_finish() in library/ccm.c allows attackers to obtain adjacent CCM context data via invocation of the multipart CCM API with an oversized tag_len parameter. This is caused by missing validation of the tag_len parameter against the size of the internal 16-byte authentication buffer. The issue affects the public multipart CCM API in Mbed TLS 3.x, where mbedtls_ccm_finish() can be invoked directly by applications. In Mbed TLS 4.x versions prior to the fix, the same missing validation exists in the internal implementation; however, the function is not exposed as part of the public API. Exploitation requires application-level invocation of the multipart CCM API.","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 n/a","id":"CVE-2026-34876","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":"Deserialization in n/a","id":"CVE-2026-34877"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2026-34875"},"products":["n/a"],"published":"2026-04-02","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2026-34875","kev_date_added":null,"published":"2026-04-01"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-49195","kev_date_added":null,"published":"2024-10-15"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2024-45158","kev_date_added":null,"published":"2024-09-05"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2024-45159","kev_date_added":null,"published":"2024-09-05"},{"cvss_score":9.8,"headline":"Mbed TLS 3.2.x through 3.4.x before 3.5 has a Buffer Overflow that can lead to remote Code execution.","id":"CVE-2023-45199","kev_date_added":null,"published":"2023-10-07"},{"cvss_score":9.1,"headline":"An issue was discovered in Mbed TLS 3.5.0 through 4.0.0.","id":"CVE-2026-34873","kev_date_added":null,"published":"2026-04-01"},{"cvss_score":9.1,"headline":"In Mbed TLS 3.3.0 through 3.5.2 before 3.6.0, a malicious client can cause information disclosure or a denial of service because of a stack","id":"CVE-2024-30166","kev_date_added":null,"published":"2024-04-03"}],"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-04-02","vendors":["n/a"]},"summary":"Attackers can read adjacent memory via oversized tag_len in Mbed TLS CCM API, potentially exposing sensitive context data.","url":"https://insights.sbomify.com/CVE-2026-34876/"}