Skip to content
Fencer Intel
medium 5.9

CVE-2026-86983 json

VOPRF blind and evaluate APIs do not enforce the RFC 9497 input length limit

published 22d ago modified 7d ago also EUVD-2026-112556 , GHSA-jwv7-rv4f-rff2

Unreviewed: the maintainers' own advisory

Published by the maintainers on their GitHub repository apple/swift-crypto. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 20%
public exploits
0
none known

Summary

A remote attacker may be able to terminate a process that passes attacker-controlled input to the P-384 VOPRF API without bounding its length. This vulnerability is addressed in swift-crypto version 5.0.3.

Patch / fix

  • Apple swift-crypto 5.0.3

Is CVE-2026-86983 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-86983 updated cvss 7.5

swift-crypto: swift-crypto: Denial of Service via unbounded input to the P-384 VOPRF API

  • Red Hat Hardened Images swift-lang 6.4.2-0.2.hum1, swift-lang-runtime 6.4.2-0.2.hum1
    fixed: vendor fix RHSA-2026:93977

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
7d ago

Exploit prediction

0.28% chance of exploitation in the next 30 days, higher than 20% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CISA ADP 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Apple swift-crypto

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

The maintainers of apple/swift-crypto published their own advisory on GitHub. Reviewed sources take precedence over it.