How severe is GHSA-77mv-mp2j-gxxh?

GHSA-77mv-mp2j-gxxh has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-77mv-mp2j-gxxh?

GHSA-77mv-mp2j-gxxh affects the following packages: 3f/pygmentize (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-77mv-mp2j-gxxh?

Update 3f/pygmentize to 1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-77mv-mp2j-gxxh is resolved across your whole dependency graph.

How do I detect GHSA-77mv-mp2j-gxxh in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for 3f/pygmentize, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-77mv-mp2j-gxxh if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-77mv-mp2j-gxxh actively exploited in the wild?

No public exploit code has been indexed for GHSA-77mv-mp2j-gxxh yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-77mv-mp2j-gxxh published, and has it been updated?

GHSA-77mv-mp2j-gxxh was published on May 15, 2024 and was last updated on November 29, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

HIGH severity

pygmentize Remote Code ExecutionGHSA-77mv-mp2j-gxxh

HIGHFix: dedalozzo/pygmentize#3

GHSA-77mv-mp2j-gxxh is a high-severity (CVSS 8.1) remote code execution vulnerability in 3f/pygmentize. A fix is available for 3f/pygmentize — see the affected versions and patch details below.

Published

May 15, 2024

Updated

Nov 29, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 29, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘3f/pygmentize

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

pygmentize is prone to remote code execution due to an unsafe sanitazation of user input when passed to the highlight function.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`3f/pygmentize`	all versions	1.2`composer require 3f/pygmentize:^1.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for 3f/pygmentize, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update 3f/pygmentize to 1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-77mv-mp2j-gxxh is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

pygmentize is prone to remote code execution due to an unsafe sanitazation of user input when passed to the `highlight` function.

O3 Security · Impact-Aware SCA

Is GHSA-77mv-mp2j-gxxh in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works