Security readout for executives and security teams
Plain-English summary
CVE-2025-13763 is a memory-safety issue in OpenSC's libopensc. A malicious smart card or USB device could cause sensitive information disclosure or an application crash. It requires a crafted physical device or smart card response, so urgency is highest for environments that rely on smart cards or accept external security tokens.
Executive priority
Treat this as a moderate, targeted risk. It is not shown as actively exploited, but it can affect authentication infrastructure and sensitive memory exposure where smart-card workflows exist. Prioritize patch tracking and device-control enforcement over emergency response.
Technical view
Multiple uninitialized variable uses in libopensc may be reached through crafted APDU responses from a USB device or smart card. The CVSS 3.1 score is 5.7 with physical attack vector, high complexity, no privileges, no user interaction, high confidentiality impact, and high availability impact.
Likely exposure
Confirmed affected entries include the opensc package on Red Hat Enterprise Linux 7, 8, 9, and 10. Exposure is most relevant on systems where OpenSC processes smart cards, USB tokens, or similar devices, especially if devices are not tightly controlled.
Exploitation context
The bundle does not show CISA KEV listing or other evidence of active exploitation. Practical exploitation requires a crafted USB device or smart card that returns specially crafted APDU responses, making opportunistic remote exploitation unlikely from the provided evidence.
Researcher notes
Evidence points to CWE-457 in libopensc with crafted APDU response handling as the trigger. The source bundle does not provide fixed versions, commit details, proof-of-concept status, or broader affected-platform data beyond the listed Red Hat products and OpenSC references.
Mitigation direction
- Check Red Hat and OpenSC guidance for fixed opensc packages or advisories.
- Update affected RHEL systems when vendor-provided opensc fixes are available.
- Restrict use of untrusted smart cards and USB security tokens.
- Apply endpoint controls limiting unauthorized USB or smart card devices.
- Prioritize systems handling sensitive authentication or certificate material.
Validation and detection
- Inventory RHEL 7, 8, 9, and 10 hosts with opensc installed.
- Identify applications using OpenSC, PKCS#11, smart cards, or USB tokens.
- Verify installed opensc versions against Red Hat and OpenSC advisories.
- Review whether untrusted physical devices can be attached to exposed systems.
- Check logs for unexplained smart-card application crashes or abnormal token interactions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-457: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-13763 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H0.55.2redhatVulnerability scoring details
Base CVSS 3.1 score
5.7MediumVector: CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineredhat
Reported to Red Hat.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineredhat
Made public.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://access.redhat.com/security/cve/CVE-2025-13763CVE reference, redhat · vdb-entry, x_refsource_REDHAT
- RHBZ#2417581CVE reference, redhat · issue-tracking, x_refsource_REDHAT
- https://github.com/OpenSC/OpenSC/security/advisories/GHSA-2v44-fq35-98vvCVE reference, redhat
- https://github.com/OpenSC/OpenSC/wiki/CVE-2025-13763CVE reference, redhat
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Uninitialized Variable
Use of Uninitialized Variable represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.