Perltidy Project maintains a focused code-formatting utility for Perl that, while narrowly scoped, sits in development and build pipelines where it processes untrusted input. The durable signal in its vulnerability profile centers on file-system access and privilege-boundary issues, including improper access control and link-following weaknesses that can arise when a formatter operates on source trees with mixed trust levels. Live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Perltidy Project over time
Signals from CVEs in this vendor scope (2 CVEs).
2 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2016-10374MEDIUM perltidy through 20160302, as used by perlcritic, check-all-the-things, and other software, relies on the current working directory for certain output files and does not have a sym | May 17, 2017 | 5.5 | 20 | NO | NO |
CVE-2014-2277HIGH The make_temporary_filename function in perltidy 20120701-1 and earlier allows local users to obtain sensitive information or write to arbitrary files via a symlink attack, related | Oct 17, 2017 | 7.1 | 18 | NO | NO |
Signals from CVEs in this vendor scope (2 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Perltidy Project.
Media articles that mention a CVE ID that affects a product developed by Perltidy Project — matched by CVE ID, not by vendor name.