CVE-2026-4539: pygments archetype.py AdlLexer redos

Published Mar 22, 2026
·
Updated

A security flaw has been discovered 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. The attack is only possible with local access. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

Affected Software

4 affected componentsFixes available
pypi/pygments<=2.19.2
pip/Pygments<=2.19.2
IBM Db2 Genius Hub<=1.1, 1.1.1, 1.1.2
IBM Agentics<=1.0

Event History

Mar 22, 2026
CVE Published
via MITRE·05:35 AM
Data Sourced
via MITRE·05:35 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:16 AM
DescriptionSeverityWeakness
Advisory Published
via GitHub·06:30 AM
Data Sourced
via GitHub·06:30 AM
DescriptionSeverityWeaknessAffected Software
Jul 13, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-4539?

CVE-2026-4539 has a severity rating that indicates it can lead to performance degradation due to inefficient regular expression processing.

2

How do I fix CVE-2026-4539?

To fix CVE-2026-4539, upgrade pygments to a version higher than 2.19.2 that does not contain this vulnerability.

3

What is the impact of CVE-2026-4539?

The impact of CVE-2026-4539 is that it allows for denial of service attacks through excessive resource consumption when using the AdlLexer function.

4

Which versions of pygments are affected by CVE-2026-4539?

Pygments versions up to and including 2.19.2 are affected by CVE-2026-4539.

5

Is there a workarounds for CVE-2026-4539?

While the best practice is to upgrade, a temporary workaround is to avoid using the AdlLexer for applications where regex performance is critical.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203