https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-06T17:18:09.020425+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-26077 EUVD-2026-26077 2026-10-06T17:18:09.023572+00:00 EUVD-2026-26077 https://cve.radiocsirt.org/vuln/fkie_cve-2021-28681 fkie_cve-2021-28681 2026-10-06T17:18:09.023616+00:00

Pion WebRTC before 3.0.15 didn't properly tear down the DTLS Connection when certificate verification failed. The PeerConnectionState was set to failed, but a user could ignore that and continue to use the PeerConnection. )A WebRTC implementation shouldn't allow the user to continue if verification has failed.)

 https://cve.radiocsirt.org/vuln/ghsa-74xm-qj29-cq8p GHSA-74xm-qj29-cq8p — In github.com/pion/webrtc, failed DTLS certificate verification doesn't stop data channel communication 2026-10-06T17:18:09.023663+00:00

Affected: Go: github.com/pion/webrtc/v3

### 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: * Open an issue in https://github.com/pion/webrtc * Email us at [team@pion.ly](mailto:team@pion.ly)

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

 https://cve.radiocsirt.org/vuln/gsd-2021-28681 gsd-2021-28681 2026-10-06T17:18:09.023718+00:00 gsd-2021-28681