During an address list folding when a separating comma ends up on a folded line and that line is to be unicode-encoded then the separator itself is also unicode-encoded. Expected behavior is that the separating comma remains a plan comma. This can result in the address header being misinterpreted by some mail servers.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2025-1795US | — | — | ||
During an address list folding when a separating comma ends up on a folded line and that line is to be unicode-encoded then the separator itself is also unicode-encoded. Expected b… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/python/cpython/commit/09fab93c3d857496c0bd162797fab816c311ee48FIX
- https://github.com/python/cpython/commit/70754d21c288535e86070ca7a6e90dcb670b8593FIX
- https://github.com/python/cpython/commit/9148b77e0af91cdacaa7fe3dfac09635c3fe9a74FIX
- https://github.com/python/cpython/commit/a4ef689ce670684ec132204b1cd03720c8e0a03dFIX
- https://github.com/python/cpython/commit/d4df3c55e4c5513947f907f24766b34d2ae8c090FIX
- https://github.com/python/cpython/issues/100884REPORT
- https://github.com/python/cpython/pull/100885WEB
- https://github.com/python/cpython/pull/119099WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan