# CVE-2026-40510: OpenSC < 0.27.0-rc1 Stack Buffer Overflow via piv_process_history() in card-piv.c > A stack buffer overflow in OpenSC allows physically present attackers to execute arbitrary code via a crafted PIV smart card. - **Severity:** Low 1.0 (`CVSS:4.0/AV:P/AC:H/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 29 May 2026 - **Updated:** 14 Jul 2026 - **Also known as:** AZL-89150, CLSA-2026-1781267272, GHSA-7rrw-cv3r-3cgg, SUSE-SU-2026:23478-1, SUSE-SU-2026:23527-1, SUSE-SU-2026:23543-1, SUSE-SU-2026:23697-1, SUSE-SU-2026:23717-1, SUSE-SU-2026:4108-1, SUSE-SU-2026:4122-1, SUSE-SU-2026:4123-1, openSUSE-SU-2026:21820-1 ## What is CVE-2026-40510? CVE-2026-40510 is a low-severity memory corruption vulnerability in Opensc Project Opensc, published on 29 May 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. ### Official description OpenSC before 0.27.0-rc1, fixed in commit 3f24f0b, contains a stack buffer overflow vulnerability in piv_process_history() in src/libopensc/card-piv.c that allows physically present attackers to trigger memory corruption by presenting a crafted PIV smart card or USB device returning a URL field longer than 118 bytes in the Key History Object ASN.1 response. Weakness: CWE-121 (Stack-based Buffer Overflow) ## Which versions are affected by CVE-2026-40510? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `opensc` | SUSE:Linux Enterprise Micro 5.3 | All versions | 0.22.0-150400.3.20.1 | | `opensc` | SUSE:Linux Enterprise Micro 5.4 | All versions | 0.22.0-150400.3.20.1 | | `opensc` | SUSE:Linux Enterprise Micro 5.5 | All versions | 0.22.0-150400.3.20.1 | | `opensc` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 0.22.0-150600.11.14.1 | | `opensc` | SUSE:Linux Enterprise Server 16.0 | All versions | 0.26.1-160000.4.1 | | `opensc` | SUSE:Linux Enterprise Server 16.0 | All versions | 0.26.1-160000.4.1 | | `opensc` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 0.13.0-3.39.1 | | `opensc` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 0.26.1-160000.4.1 | | `opensc` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 0.26.1-160000.4.1 | | `opensc` | SUSE:Linux Micro 6.0 | All versions | 0.24.0-7.1 | | `opensc` | SUSE:Linux Micro 6.1 | All versions | 0.24.0-slfo.1.1_5.1 | | `opensc` | SUSE:Linux Micro 6.2 | All versions | 0.26.1-160000.4.1 | | `opensc` | openSUSE:Leap 16.0 | All versions | 0.26.1-160000.4.1 | Products: Opensc Project Opensc. ## How do I fix CVE-2026-40510? Upgrade to a fixed version. ## Is CVE-2026-40510 being exploited? There is no known exploitation of CVE-2026-40510 in the wild and no public exploit code. ## Other vulnerabilities in Opensc Project Opensc - [CVE-2021-34193](https://insights.sbomify.com/CVE-2021-34193/): Memory corruption in n/a (high 7.5) - [CVE-2019-16058](https://insights.sbomify.com/CVE-2019-16058/): Memory corruption in n/a (high 7.5) - [CVE-2019-6502](https://insights.sbomify.com/CVE-2019-6502/): Denial of service in n/a (high 7.5) - [CVE-2023-2977](https://insights.sbomify.com/CVE-2023-2977/): Memory corruption in OpenSC (high 7.1) - [CVE-2019-20792](https://insights.sbomify.com/CVE-2019-20792/): Use after free in n/a (medium 6.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-40510 and fix it if it is affected. What it is: CVE-2026-40510 is a low-severity memory corruption vulnerability in Opensc Project Opensc, published on 29 May 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. Exploitation: There is no known exploitation of CVE-2026-40510 in the wild and no public exploit code. Affected product: Opensc Project Opensc. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-40510/ (Markdown: https://insights.sbomify.com/CVE-2026-40510/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40510 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40510 - OSV: https://osv.dev/vulnerability/CVE-2026-40510 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-40510/ Summaries are generated and may contain mistakes; the official description above is the record.