CVE-2026-56813

Cookie attribute injection in Plug.Conn.Cookies.encode/2

LOW
2.1
CVSS Score
Published: July 10, 2026 at 12:51 PM UTC
Updated: October 24, 2026 at 11:10 PM UTC
1 product affected across 1 vendorPlug

Using plug by elixir-plug?

Get instant alerts when new vulnerabilities affect plug - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
LOW2.1
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

Improper Neutralization of Parameter/Argument Delimiters vulnerability in elixir-plug plug allows an attacker to inject or override HTTP cookie attributes. The Plug.Conn.Cookies.encode/2 function in lib/plug/conn/cookies.ex builds the Set-Cookie response header by interpolating the cookie value and its path, domain, same_site, and extra attributes directly into the header without neutralizing the ';' delimiter that separates cookie attributes. An application that places attacker-controlled data into a cookie value or attribute (for example via Plug.Conn.put_resp_cookie/4 when reflecting a username or preference) lets an attacker inject a ';' to append or override cookie attributes (such as Domain and Path scope, or dropping the Secure and HttpOnly flags), enabling cookie tossing and session fixation. Carriage return, line feed, and null bytes are rejected by Plug.Conn header validation, so HTTP response splitting is not possible, but attribute injection through ';' is not prevented. This issue affects plug: from 0.1.0 before 1.16.6, from 1.17.0 before 1.17.4, from 1.18.0 before 1.18.5, from 1.19.0 before 1.19.5, from 1.20.0 before 1.20.3.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

All versions0.1.01.17.01.18.01.19.11.20.0f26876aa67aaeb38e616638aa3efbcc2fe2906a5
Affected range stops below 1.16.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.17.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.18.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.19.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.20.3, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

2.1LOWEEF
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-141

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card