CVE-2026-4539 | pygments up to 2.19.2 archetype.py AdlLexer redos (Issue 3058)
VulDBArchived Mar 21, 2026✓ Full text saved
A vulnerability, which was classified as problematic , was found in pygments up to 2.19.2 . The impacted element is the function AdlLexer of the file pygments/lexers/archetype.py . The manipulation results in inefficient regular expression complexity. This vulnerability is identified as CVE-2026-4539 . The attack is only possible with local access. Additionally, an exploit exists. The project was informed of the problem early through an issue report but has not responded yet.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-352327 · CVE-2026-4539 · ISSUE 3058
PYGMENTS UP TO 2.19.2 ARCHETYPE.PY ADLLEXER REDOS
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
3.0 $0-$5k 2.14+
Summaryinfo
A vulnerability has been found in pygments up to 2.19.2 and classified as problematic. This affects the function AdlLexer of the file pygments/lexers/archetype.py. This manipulation causes redos. This vulnerability is tracked as CVE-2026-4539. The attack is restricted to local execution. Moreover, an exploit is present. The project was informed of the problem early through an issue report but has not responded yet.
Detailsinfo
A vulnerability has been found in pygments up to 2.19.2 and classified as problematic. Affected by this vulnerability is the function AdlLexer of the file pygments/lexers/archetype.py. The manipulation with an unknown input leads to a redos vulnerability. The CWE definition for the vulnerability is CWE-1333. The product uses a regular expression with an inefficient, possibly exponential worst-case computational complexity that consumes excessive CPU cycles. As an impact it is known to affect availability.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-4539. The exploitation appears to be easy. Attacking locally is a requirement. Technical details and also a public exploit are known. The attack technique deployed by this issue is T1449.003 according to MITRE ATT&CK.
It is possible to download the exploit at github.com. It is declared as proof-of-concept. The project was informed of the problem early through an issue report but has not responded yet.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Productinfo
Name
pygments
Version
2.19.0
2.19.1
2.19.2
Website
Product: https://github.com/pygments/pygments/
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 3.3
VulDB Meta Temp Score: 3.0
VulDB Base Score: 3.3
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Redos
CWE: CWE-1333 / CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: no mitigation known
Status: 🔍
0-Day Time: 🔒
Timelineinfo
03/21/2026 Advisory disclosed
03/21/2026 +0 days VulDB entry created
03/21/2026 +0 days VulDB entry last update
Sourcesinfo
Product: github.com
Advisory: 3058
Status: Not defined
CVE: CVE-2026-4539 (🔒)
GCVE (CVE): GCVE-0-2026-4539
GCVE (VulDB): GCVE-100-352327
scip Labs: https://www.scip.ch/en/?labs.20161013
Entryinfo
Created: 03/21/2026 10:15
Changes: 03/21/2026 10:15 (56)
Complete: 🔍
Submitter: ybdesire
Cache ID: 99:81D:101
Submitinfo
Accepted
Submit #774685: pygments <=2.19.2 Denial of Service (by ybdesire)
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸