CVE-2026-8612: WWW::Mechanize::Cached versions before 2.00 for Perl deserialize cached HTTP responses from a world-writable on-disk cache, enabling local response forgery and code execution

Published May 15, 2026
·
Updated

WWW::Mechanize::Cached versions before 2.00 for Perl deserialize cached HTTP responses from a world-writable on-disk cache, enabling local response forgery and code execution.

With no explicit cache backend, WWW::Mechanize::Cached constructs a default Cache::FileCache under /tmp/FileCache without overriding the backend's documented directoryumask of 000, so the cache root and its subdirectories are created mode 0777 with no sticky bit. Cache entries are named by sha1hex of the request and read back through Storable::thaw on the next cache hit.

A local attacker with write access to the cache tree can replace a victim's cache entry for a known URL with an arbitrary frozen HTTP::Response blob, causing the victim's next get() of that URL to return attacker controlled response bytes. Because the bytes are passed to Storable::thaw, a victim process that has loaded any class with a side-effectful STORABLEthaw, DESTROY, or overload hook can be escalated to arbitrary code execution.

Affected Software

2 affected components
cpan/WWW-Mechanize-Cached<2.00
Oalders Www\<2.00

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade WWW::Mechanize::Cached to a version that resolves this vulnerability.

    Fixed in 2.00
  2. Configuration

    With the default cache backend (Cache::FileCache under /tmp/FileCache when no explicit backend is configured), change the cache backend configuration to avoid creating cache directories with umask 000 (mode 0777, no sticky bit). Ensure the cache root/subdirectories are created with safer permissions by setting directory_umask to a value that prevents world-writable (0777) directories.

    Cache::FileCache (default backend used by WWW::Mechanize::Cached) directory_umask = 000

Event History

May 15, 2026
CVE Published
via MITRE·01:11 AM
Data Sourced
via MITRE·01:11 AM
RemedyDescriptionWeakness
Data Sourced
via NVD·02:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Jun 29, 58424
Event
via FIRST·03:27 PM

Frequently Asked Questions

1

What is the severity of CVE-2026-8612?

CVE-2026-8612 is classified as a critical vulnerability due to its potential for local response forgery and code execution.

2

How do I fix CVE-2026-8612?

To fix CVE-2026-8612, upgrade to WWW::Mechanize::Cached version 2.00 or later.

3

What systems are affected by CVE-2026-8612?

CVE-2026-8612 affects all versions of WWW::Mechanize::Cached prior to 2.00 that use a world-writable cache.

4

What is the impact of CVE-2026-8612?

The impact of CVE-2026-8612 includes local response forgery and the possibility of arbitrary code execution.

5

When was CVE-2026-8612 reported?

CVE-2026-8612 was reported in 2026, highlighting vulnerabilities in caching mechanisms.

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