{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-43823 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-43823 is a high-severity vulnerability in Apple swift-crypto, published on 23 Jul 2026."},"fix_prompt":"Check this codebase for CVE-2026-43823 and fix it if it is affected.\n\nWhat it is: CVE-2026-43823 is a high-severity vulnerability in Apple swift-crypto, published on 23 Jul 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-43823 exists.\n\nAffected product: Apple swift-crypto. 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-43823/ (Markdown: https://insights.sbomify.com/CVE-2026-43823/index.md)","id":"CVE-2026-43823","markdown":"https://insights.sbomify.com/CVE-2026-43823/index.md","name":"CVE-2026-43823","record":{"aliases":["GHSA-8q93-f6xh-4f6f"],"analysis":null,"analysis_generated_by":null,"assigner":"apple","cpe":[{"product":"swift-crypto","vendor":"apple"}],"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-415","name":"Double Free"}],"description":"When initializing an RSA public key from DER or PEM bytes throws an error, the EVP_PKEY* is double-freed: first in the catch block, then in the deinit. This can lead to a crash on future memory allocations. This double-free manifests when BoringSSL cannot decode the public key from the bytes provided. This vulnerability is addressed in swift-crypto version 4.5.1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"When initializing an RSA public key from DER or PEM bytes throws an error, the EVP_PKEY* is double-freed: first in the catch block, then in the deinit.","id":"CVE-2026-43823","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in Argo CD","id":"CVE-2026-43824"},"packages":[],"prev":{"headline":"Use after free in iOS and iPadOS","id":"CVE-2026-43822"},"products":["swift-crypto"],"published":"2026-07-23","related":[{"cvss_score":7.5,"headline":"Swift Crypto: X-Wing HPKE Decapsulation Accepts Malformed Ciphertext Length","id":"CVE-2026-28815","kev_date_added":null,"published":"2026-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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-23","vendors":["Apple"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-43823/"}