{"answers":{"affected":"2 open source packages ship an affected version, including swift-crypto. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28815 exists.","fix":"Upgrade swift-crypto to 4.3.1 or later.","what":"CVE-2026-28815 is a high-severity vulnerability in Apple macOS, published on 3 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-28815 and fix it if it is affected.\n\nWhat it is: CVE-2026-28815 is a high-severity vulnerability in Apple macOS, published on 3 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28815 exists.\n\nAffected packages and fixed versions:\n- swift-crypto (SwiftURL): affected from 4.0.0; fixed in 4.3.1\n- swift-crypto (SwiftURL): affected from 4.0.0; fixed in 4.3.1\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-28815/ (Markdown: https://insights.sbomify.com/CVE-2026-28815/index.md)","id":"CVE-2026-28815","markdown":"https://insights.sbomify.com/CVE-2026-28815/index.md","name":"CVE-2026-28815","record":{"aliases":["GHSA-9m44-rr2w-ppp7"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Swift crypto library","requires_auth":"none","summary":"A remote attacker can trigger an out-of-bounds read in the swift-crypto library, potentially causing crashes or memory disclosure.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","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-125","name":"Out-of-bounds Read"}],"description":"A remote attacker can supply a short X-Wing HPKE encapsulated key and trigger an out-of-bounds read in the C decapsulation path, potentially causing a crash or memory disclosure depending on runtime protections. This issue is fixed in swift-crypto version 4.3.1.","ecosystems":["SwiftURL"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"Swift Crypto: X-Wing HPKE Decapsulation Accepts Malformed Ciphertext Length","id":"CVE-2026-28815","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"SwiftURL","product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Path traversal in macOS","id":"CVE-2026-28816"},"packages":[{"ecosystem":"SwiftURL","fixed":["4.3.1"],"introduced":["4.0.0"],"last_affected":[],"package":"swift-crypto","purl":null,"source":"GHSA-9m44-rr2w-ppp7"},{"ecosystem":"SwiftURL","fixed":["4.3.1"],"introduced":["4.0.0"],"last_affected":[],"package":"swift-crypto","purl":"pkg:swift/swift-crypto","source":"GHSA-9m44-rr2w-ppp7"}],"prev":{"headline":"Apache JSPWiki: Pre-Authentication Arbitrary Wiki Markup Rendering","id":"CVE-2026-28814"},"products":["macOS"],"published":"2026-04-03","related":[{"cvss_score":7.5,"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","kev_date_added":null,"published":"2026-07-23"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-04-03","vendors":["Apple"]},"summary":"A remote attacker can trigger an out-of-bounds read in the swift-crypto library, potentially causing crashes or memory disclosure.","url":"https://insights.sbomify.com/CVE-2026-28815/"}