{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-49010 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2025-49010 is a low-severity memory corruption vulnerability in Opensc Project Opensc, published on 30 Mar 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-2025-49010 and fix it if it is affected.\n\nWhat it is: CVE-2025-49010 is a low-severity memory corruption vulnerability in Opensc Project Opensc, published on 30 Mar 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-2025-49010 in the wild and no public exploit code.\n\nAffected product: Opensc Project Opensc. 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-49010/ (Markdown: https://insights.sbomify.com/CVE-2025-49010/index.md)","id":"CVE-2025-49010","markdown":"https://insights.sbomify.com/CVE-2025-49010/index.md","name":"CVE-2025-49010","record":{"aliases":["AZL-81183","BELL-CVE-2025-49010","DEBIAN-CVE-2025-49010","GHSA-q5cf-5wmx-9wh4","UBUNTU-CVE-2025-49010"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Smart card middleware","requires_auth":"none","summary":"An attacker with physical access can trigger a stack-buffer-overflow write via a crafted smart card, potentially leading to code execution.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"opensc","vendor":"opensc_project"}],"cvss":{"score":3.8,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:P/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"OpenSC is an open source smart card tools and middleware. Prior to version 0.27.0, an attacker with physical access to the computer at the time user or administrator uses a token can cause a stack-buffer-overflow write in GET RESPONSE. The attack requires crafted USB device or smart card that would present the system with specially crafted responses to the APDUs. This issue has been patched in version 0.27.0.","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":"OpenSC: Stack-buffer-overflow WRITE in GET RESPONSE","id":"CVE-2025-49010","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"opensc_project:opensc","products":["opensc_project:opensc"],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"SpiceDB checks involving relations with caveats can result in no permission when permission is expected","id":"CVE-2025-49011"},"packages":[],"prev":{"headline":"Para Inserts Sensitive Information into Log File for Facebook authentication","id":"CVE-2025-49009"},"products":["OpenSC"],"published":"2026-03-30","related":[{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2021-34193","kev_date_added":null,"published":"2023-08-22"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2019-16058","kev_date_added":null,"published":"2019-09-06"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2019-6502","kev_date_added":null,"published":"2019-01-22"},{"cvss_score":7.1,"headline":"Memory corruption in OpenSC","id":"CVE-2023-2977","kev_date_added":null,"published":"2023-06-01"},{"cvss_score":6.8,"headline":"Use after free in n/a","id":"CVE-2019-20792","kev_date_added":null,"published":"2020-04-29"},{"cvss_score":6.8,"headline":"Memory corruption in n/a","id":"CVE-2018-16391","kev_date_added":null,"published":"2018-09-03"},{"cvss_score":6.8,"headline":"Memory corruption in n/a","id":"CVE-2018-16392","kev_date_added":null,"published":"2018-09-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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-30","vendors":["OpenSC"]},"summary":"An attacker with physical access can trigger a stack-buffer-overflow write via a crafted smart card, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2025-49010/"}