CVE-2015-8557: The FontManager._get_nix_font_path function in formatters/img.py in Pygments 1.2.2 through 2.0.2 allows remote attackers to execute…
Noroxi assessment
Priority: Monitor (action score 38/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 6.7% (FIRST EPSS); higher than 94% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- Fixed version: pygments (Debian:12) 2.0.1+dfsg-2; pygments (Debian:6.0) 1.3.1+dfsg-1+deb6u11; pygments (Debian:7) 1.5+dfsg-1+deb7u1.
Low priority for now. Upgrade to pygments (Debian:12) 2.0.1+dfsg-2; pygments (Debian:6.0) 1.3.1+dfsg-1+deb6u11; pygments (Debian:7) 1.5+dfsg-1+deb7u1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The FontManager._get_nix_font_path function in formatters/img.py in Pygments 1.2.2 through 2.0.2 allows remote attackers to execute arbitrary commands via shell metacharacters in a font name.
- Published
- Jan 8, 2016
- Updated
- Jun 16, 2026
- EPSS
- 6.7% · 94th percentile
- CWE
- CWE-78
Report tools
Action score
38
Low priority for now.
- CVSS
- 36 / 40 · 9.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 6.7%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| pygments | pygments | cpe:2.3:a:pygments:pygments |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux12.04
- canonical ubuntu linux14.04
- canonical ubuntu linux15.04
- canonical ubuntu linux15.10
- pygments pygments1.2.2
- pygments pygments1.3
- pygments pygments1.3.1
- pygments pygments1.4
+4 more rows
- pygments pygments1.5
- pygments pygments1.6
- pygments pygments2.0
- pygments pygments2.0.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | pygments | before 2.0.1+dfsg-2 | 2.0.1+dfsg-2 |
| Debian:6.0 | pygments | before 1.3.1+dfsg-1+deb6u11 | 1.3.1+dfsg-1+deb6u11 |
| Debian:7 | pygments | before 1.5+dfsg-1+deb7u1 | 1.5+dfsg-1+deb7u1 |
| Debian:8 | pygments | before 2.0.1+dfsg-1.1+deb8u1 | 2.0.1+dfsg-1.1+deb8u1 |
| PyPI | pygments | from 1.2.2 · before 2.1 | 2.1 |
Same product
pygments: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-20270An infinite loop in SMLLexer in Pygments versions 1.5 to 2.7.3 may lead to denial of service when performing syntax highlighting of a…31Monitor
- CVE-2021-27291In pygments 1.1+, fixed in 2.7.4, the lexers used to parse programming languages rely heavily on regular expressions.31Monitor
- CVE-2022-40896A ReDoS issue was discovered in pygments/lexers/smithy.py in pygments through 2.15.0 via SmithyLexer.22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:pygments | 2.0.1+dfsg-2 · Debian:12 | Package registry (OSV) |
| PyPI:pygments | 2.1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')CVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
nvd-primary
Root cause
User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.
The bug in code
The whole CWE-78 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const host = req.body.host;
exec("ping -c 1 " + host, onResult);Fixed
const host = req.body.host;
if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);
execFile("ping", ["-c", "1", host], onResult);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Command DelimitersCAPEC-15likelihood: High · High
- Exploiting Multiple Input Interpretation LayersCAPEC-43likelihood: Medium · High
- Argument InjectionCAPEC-6likelihood: High · High
- OS Command InjectionCAPEC-88likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- www.debian.org/security/2016/dsa-3445
- www.openwall.com/lists/oss-security/2015/12/14/17
- www.openwall.com/lists/oss-security/2015/12/14/6
- www.oracle.com/technetwork/topics/security/bulletinjan2016-2867206.html
- www.ubuntu.com/usn/USN-2862-1
- bitbucket.org/birkenfeld/pygments-main/pull-requests/501/fix-shell-injection-in/diff
- security.gentoo.org/glsa/201612-05
Vendor advisories and official records. Exploit/PoC links are deliberately left out.