Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
MEDIUM severity

GHSA-74xm-qj29-cq8p

MEDIUMFix: pion/webrtc#1709

GHSA-74xm-qj29-cq8p is a medium-severity (CVSS 5.3) vulnerability in github.com/pion/webrtc/v3. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-74xm-qj29-cq8p is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

In github.com/pion/webrtc, failed DTLS certificate verification doesn't stop data channel communication

Also known asCVE-2021-28681GO-2021-0104
Published
May 25, 2021
Updated
Jul 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Jul 8, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐹github.com/pion/webrtc/v3

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

Data channel communication was incorrectly allowed with users who have failed DTLS certificate verification.

This attack requires

  • Attacker knows the ICE password.
  • Only take place during PeerConnection handshake.

This attack can be detected by monitoring PeerConnectionState in all versions of Pion WebRTC.

Patches

Users should upgrade to v3.0.15.

The exact patch is https://github.com/pion/webrtc/commit/545613dcdeb5dedb01cce94175f40bcbe045df2e

Workarounds

Users should listen for when PeerConnectionState changes to PeerConnectionStateFailed. When it enters this state users should not continue using the PeerConnection.

For more information

If you have any questions or comments about this advisory:

Thank you to https://github.com/Gaukas for discovering this.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/pion/webrtc/v3all versions3.0.15
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/pion/webrtc/v3. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/pion/webrtc/v3 to 3.0.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-74xm-qj29-cq8p is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-74xm-qj29-cq8p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-74xm-qj29-cq8p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Data channel communication was incorrectly allowed with users who have failed DTLS certificate verification. This attack requires * Attacker knows the ICE password. * Only take place during PeerConnection handshake. This attack can be detected by monitoring `PeerConnectionState` in all versions of Pion WebRTC. ### Patches Users should upgrade to v3.0.15. The exact patch is https://github.com/pion/webrtc/commit/545613dcdeb5dedb01cce94175f40bcbe045df2e ### Workarounds Users should listen for when `PeerConnectionState` changes to `PeerConnectionStateFailed`. When it enters this
O3 Security · Impact-Aware SCA

Is GHSA-74xm-qj29-cq8p in your dependencies?

O3 detects GHSA-74xm-qj29-cq8p across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.