Skip to main content
VulnerabilityPublished

CVE-2026-8612: OALDERS WWW::Mechanize::Cached · Incorrect Permissions

Affects OALDERS WWW::Mechanize::CachedSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 2.00 when convenient.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.00
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade WWW::Mechanize::Cached and WWW-Mechanize-Cached to 2.00.

Affected software

ProductAffectedFixed in
OALDERSWWW::Mechanize::CachedAffected
  • <2.00
Fixed in
  • 2.00
GitHubWWW-Mechanize-Cachedpkg:github/WWW-Mechanize-CachedOther threatsAffected
  • <2.00
Fixed in
  • 2.00

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, restrict write permissions to the cache directory to trusted users only and avoid running WWW::Mechanize::Cached in environments where untrusted local users have write access to the cache directory. Consider configuring an explicit cache backend with secure permissions if supported.

Description

CVE-2026-8612 affects WWW::Mechanize::Cached versions before 2.00 for Perl, where cached HTTP responses are stored in a world-writable directory with insecure permissions. This allows a local attacker with write access to the cache directory to replace cached responses with attacker-controlled data. When the victim process retrieves the cached response, it deserializes the data using Storable::thaw, potentially triggering arbitrary code execution if certain Perl classes with side-effectful hooks are loaded. The vulnerability arises from incorrect permission assignment (CWE-732) and unsafe deserialization (CWE-502).

References

Community reviews

Loading reviews…