# CVE-2025-13763: Libopensc: opensc: multiple uses of uninitialized variable

> Attackers with physical access can use crafted smart cards to trigger uninitialized variable usage, causing information disclosure or crashes in OpenSC.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Apr 2026
- **Updated:** 30 Jun 2026
- **Also known as:** BELL-CVE-2025-13763, DEBIAN-CVE-2025-13763, GHSA-2v44-fq35-98vv, UBUNTU-CVE-2025-13763

## What is CVE-2025-13763?

CVE-2025-13763 is a medium-severity vulnerability in OpenSC, published on 23 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Multiple uses of uninitialized variables were found in libopensc that may lead to information disclosure or application crash. An attack requires a crafted USB device or smart card that would present the system with specially crafted responses to the APDUs

Weakness: CWE-457 (Use of Uninitialized Variable)

## Which versions are affected by CVE-2025-13763?


## How do I fix CVE-2025-13763?

Apply the vendor's patch.

## Is CVE-2025-13763 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-13763 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-13763 and fix it if it is affected.

What it is: CVE-2025-13763 is a medium-severity vulnerability in OpenSC, published on 23 Apr 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-13763 exists.

Affected product: 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-2025-13763/ (Markdown: https://insights.sbomify.com/CVE-2025-13763/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-13763
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-13763
- OSV: https://osv.dev/vulnerability/CVE-2025-13763

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-13763/
Summaries are generated and may contain mistakes; the official description above is the record.