CVE-2026-86983
Description
A flaw was found in swift-crypto. A remote attacker can trigger a Denial of Service (DoS) by providing excessively long or unbounded input to an application utilizing the P-384 Verifiable Oblivious Pseudorandom Function (VOPRF) interface. Because the interface does not adequately restrict input length, processing the untrusted data can cause the application process to terminate unexpectedly.
Statement
A flaw was found in the swift-crypto package's P-384 VOPRF API implementation. A remote attacker can pass excessively long or unbounded input to an application utilizing this interface, triggering unexpected process termination and resulting in a denial of service.
Mitigation
Enforce strict payload length limits and input validation at the application boundary prior to passing untrusted data to the P-384 VOPRF interface. Where direct code changes are not immediately viable, deploy an API gateway or reverse proxy to restrict maximum request body sizes.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 7.5 | N/A | N/A |
| Attack Vector | Network | N/A | N/A |
| Attack Complexity | Low | N/A | N/A |
| Privileges Required | None | N/A | N/A |
| User Interaction | None | N/A | N/A |
| Scope | Unchanged | N/A | N/A |
| Confidentiality | None | N/A | N/A |
| Integrity Impact | None | N/A | N/A |
| Availability Impact | High | N/A | N/A |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)
When allocating resources without limits, an attacker could prevent other systems, applications, or processes from accessing the same type of resource. It can be easy for an attacker to consume many resources by rapidly making many requests or causing larger resources to be used than is needed.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
