Skip to content
Fencer Intel
critical 9.8

CVE-2019-8849 json

SwiftNIO SSL arbitrary code execution vulnerability

published 6y ago modified 4mo ago also EUVD-2022-3826 , GHSA-frg3-gpcx-968f

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.2%
EPSS 2.2% chance of exploitation in 30 days, percentile 82%
public exploits
0
none known

Summary

The issue was addressed by signaling that an executable stack is not required. This issue is fixed in SwiftNIO SSL 2.4.1. A SwiftNIO application using TLS may be able to execute arbitrary code.

Patch / fix

  • swift github.com/apple/swift-nio-ssl 2.4.1
  • Apple Swift-Ubuntu SwiftNIO SSL 2.4.1

Is CVE-2019-8849 in your dependencies? 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

Exploit prediction

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

CVSS scores

assigned by version score vector
GitHub 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected packages

ecosystem package affected fixed in
swift github.com/apple/swift-nio-ssl
>=2.0.0, <2.4.1
2.4.1

Affected products

  • Apple Swift-Ubuntu

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.