CVE-2016-10374: perltidy through 20160302, as used by perlcritic, check-all-the-things, and other software, relies on the curr

Q: How do I fix CVE-2016-10374?

perltidy: upgrade to newer than 2016-03-02. Exact commands for each OS are on this page.

Q: Is CVE-2016-10374 being exploited?

CVE-2016-10374 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2016-10374 affect?

CVE-2016-10374 affects perltidy. Severity is medium (CVSS 5.5). 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 symlink-attack protection mechanism, which allows local users t

Q: How urgent is CVE-2016-10374?

Priority 26/100. No elevated risk signals yet.

Routine

MEDIUM 5.5UPGRADE

CVE-2016-10374 is a medium-severity flaw (CVSS 5.5) affecting perltidy. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 symlink-attack protection mechanism, which allows local users to overwrite arbitrary files by creating a symlink, as demonstrated by creating a perltidy.ERR symlink that the victim cannot delete.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 75%)
CISA exploited list	No
Weakness	CWE-59
Published	2017-05-17
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: perltidy project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2017-05-17 19:29 UTCPublished CVE record published
2026-06-17 00:39 UTCUpdated Record last modified

perltidy project perltidy UPGRADE

Affected: <= 2016-03-02

Fixed in: newer than 2016-03-02

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy perltidy || rpm -q perltidy || perltidy --version

2. UPGRADE to newer than 2016-03-02 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade perltidy

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade perltidy

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2016-10374?

perltidy: upgrade to newer than 2016-03-02. Exact commands for each OS are on this page.

Is CVE-2016-10374 being exploited?

CVE-2016-10374 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2016-10374 affect?

CVE-2016-10374 affects perltidy. Severity is medium (CVSS 5.5). 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 symlink-attack protection mechanism, which allows local users t

How urgent is CVE-2016-10374?

Priority 26/100. No elevated risk signals yet.

Related CVEs

CVE-2014-2277 HIGH 7.1 UPGRADE The make_temporary_filename function in perltidy 20120701-1 and earlier allows local users to obtain sensitive

References

← Back to latest CVEs