{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-66366 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2025-66366 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-66366 is a high-severity vulnerability in Samsung Semiconductor Exynos 1280, published on 5 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2025-66366 and fix it if it is affected.\n\nWhat it is: CVE-2025-66366 is a high-severity vulnerability in Samsung Semiconductor Exynos 1280, published on 5 Nov 2026. \nExploitation: There is no known exploitation of CVE-2025-66366 in the wild and no public exploit code.\n\nAffected product: Samsung Semiconductor Exynos 1280. 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-2025-66366/ (Markdown: https://insights.sbomify.com/CVE-2025-66366/index.md)","id":"CVE-2025-66366","markdown":"https://insights.sbomify.com/CVE-2025-66366/index.md","name":"CVE-2025-66366","record":{"aliases":["GHSA-48x4-685f-c87v"],"analysis":null,"analysis_generated_by":null,"assigner":"samsungsemiconductor","cpe":[],"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-129","name":"Improper Validation of Array Index"}],"description":"Incorrect handling of unauthenticated downlink RRC Setup messages can cause the baseband to crash","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Incorrect handling of unauthenticated downlink RRC Setup messages can cause the baseband to crash","id":"CVE-2025-66366","indexable":false,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2025"},"n_packages":0,"n_references":1,"n_vendor_status":0,"next":{"headline":"Improper handling of NAS DLTransport messages may lead to a baseband crash.","id":"CVE-2025-66367"},"nickname":null,"packages":[],"prev":{"headline":"Incorrect handling of SIP packets leads to baseband crashes","id":"CVE-2025-66365"},"products":["Exynos 1280","Exynos 1330","Exynos 1380","Exynos 1480","Exynos 1580","Exynos 2400","Exynos 2500","Exynos Modem 5300","Exynos Modem 5400","Exynos Modem 5410"],"published":"2026-11-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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-11-10","vendor_status":[],"vendors":["Samsung Semiconductor"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2025-66366/"}