---
id: "CVE-2026-86983"
kind: "vulnerability"
aliases: ["CVE-2026-86983"]
title: "swift-crypto: unbounded input to P-384 VOPRF API can crash a process"
severity: "unknown"
cvss: null
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["package", "server-side", "swift", "swift-crypto"]
not_affected_if: ["no-voprf-usage"]
published_at: "2026-10-28T23:17:11+00:00"
first_seen_at: "2026-10-28T23:35:49+00:00"
updated_at: "2026-10-28T23:36:44+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-86983", "first_seen_at": "2026-10-28T23:35:49+00:00"}]
---

# swift-crypto: unbounded input to P-384 VOPRF API can crash a process

The P-384 VOPRF API in swift-crypto does not bound the length of input it accepts. A remote attacker who can pass attacker-controlled data into that API can terminate the process that handles it.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Look for `swift-crypto` in `Package.resolved` or the dependency graph and read the resolved version.
- Check whether the code calls the P-384 VOPRF API with data that arrives from outside the service.

## Fix

- Upgrade `swift-crypto` to `5.0.3` or later.
- Until upgraded, unknown for a workaround: the sources do not say.

## Timeline

- 2026-10-28T23:35:49+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-86983

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_