Skip to main content
VulnerabilityPublished

CVE-2026-103831: TrueLayer Magento 2 Plugin · Deserialization of Untrusted Data

Affects TrueLayer Magento 2 PluginSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.5 High.

Data as of 20 Nov 2026, 17:34 UTC

CVSS 4.0 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Oct 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 20 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
TrueLayerTrueLayer Magento 2 PluginAffected
  • =versions 2.4.0 through 2.4.2.
Fixed in–

AI-suggested

Until an official fix is available, restrict write access to the cache backend (e.g., Redis, Memcached) to trusted users and services only. Monitor and secure the cache infrastructure to prevent unauthorized writes. Avoid using unserialize() on untrusted data or implement strict class whitelisting if modifying the plugin code is possible.

Description

CVE-2026-103831: Insecure deserialization vulnerability in the Psr16CacheAdapter component of the TrueLayer Magento 2 Plugin, due to the use of PHP's native unserialize() function without restrictions on the classes allowed when retrieving data stored in the cache. An attacker who already has the ability to write manipulated data to the cache backend used by Magento—such as Redis or Memcached—could inject specially crafted PHP objects and trigger their deserialization, potentially leading to arbitrary code execution via gadget strings available in the application environment. Exploitation therefore requires a prerequisite condition that allows writing to the cache infrastructure, either through access to the local file system or to a cache infrastructure accessible from the Magento environment.

References

Community reviews

Loading reviews…