AI Science Tracker

Client authentication bypass when client and server connections share a session store

Pion DTLS · AI involvement attributed to Anthropic's OSS Scanner

Finding and attribution

DTLS 1.2 resumption did not distinguish client-created from server-created sessions in a shared SessionStore. A malicious server previously contacted by the application must retain the session secret and reach its listener; it can resume the outbound session, after which the listener accepts application data without its usual PSK or client-certificate checks. The advisory says WebRTC users are unaffected.

Product: Pion DTLS. AI system: Anthropic's OSS Scanner. Team / organization: Anthropic.

CVE identifiers: Not established in the cited evidence.

AI and human contribution (source account): The Pion maintainer's case-specific advisory credits Anthropic's OSS Scanner as discoverer (tracking identifier ANT-2026-ALO2G36N). It does not identify model versions or internal discovery dates.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The cited advisory documents public disclosure; it does not establish whether defenders knew of the issue or whether it was exploited before disclosure.

Remediation status: fix documented. The advisory identifies fix commit 2b234cd and the following package-version scope: v2 2.1.0–2.2.12 (no patched v2 version listed); v3 before 3.1.14, fixed 3.1.14. This source does not establish downstream deployment.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 16 Oct 2026. AI attribution dated 16 Oct 2026. Sources checked 16 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: High · highest recorded score 7.4. Documented technical effects: authentication bypass.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

  • Case-level assessment: CVSS 3.1 · 7.4 (High) · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N. Pion GitHub Security Advisory · checked 16 Nov 2026.

Case-level evidence: authentication bypass.
Prerequisites / affected scope: authentication bypass affecting listener application-data access under the stated shared-store and prior-outbound-contact conditions..
Exploitation evidence: The advisory describes a possible attack path but does not report observed exploitation.. Impact source · checked 16 Nov 2026.

Documented fix: The advisory identifies fix commit 2b234cd and the following package-version scope: v2 2.1.0–2.2.12 (no patched v2 version listed); v3 before 3.1.14, fixed 3.1.14. This source does not establish downstream deployment.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases