CVE-2026-103831

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (5th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-93363 (ENISA EUVD) · GHSA-x69j-rqv7-gx25 (GitHub Security Advisories)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.5Exploit: None knownExposed services: Not assessed

It is recommended to update the plugin to version 2.4.3 or later (from the CVE record's solution, Spanish National Cybersecurity Institute, S.A. (INCIBE)) — apply it.

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.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
34
EG Risk 34/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: It is recommended to update the plugin to version 2.4.3 or later (from the CVE record's solution, Spanish National Cybersecurity Institute, S.A. (INCIBE)). Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

It is recommended to update the plugin to version 2.4.3 or later (from the CVE record's solution, Spanish National Cybersecurity Institute, S.A. (INCIBE)). Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 6, 2026

Last Modified

October 6, 2026

Advisory Details (1)

Auto-updated Oct 6, 2026
Fix named in the CVE record's solution (Spanish National Cybersecurity Institute, S.A. (INCIBE)).
Web page

Insecure deserialization in the TrueLayer Magento 2 plugin | INCIBE-CERT | INCIBE

https://www.incibe.es/en/incibe-cert/notices/aviso/insecure-deserialization-truelayer-magento-2-plugin

Vendor Advisories for CVE-2026-103831(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 57× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-10-27 20:36 UTCEG score recompute
  7. 2026-10-27 20:36 UTCGHSA enrichmentGHSA-x69j-rqv7-gx25 · GitHub severity HIGH
  8. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  10. 2026-10-25 14:56 UTCEG score recompute
  11. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  13. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  14. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  15. 2026-10-20 19:14 UTCEG score recompute
  16. 2026-10-20 19:14 UTCGHSA enrichmentGHSA-x69j-rqv7-gx25 · GitHub severity HIGH
  17. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  18. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  20. 2026-10-18 05:09 UTCEG score recompute
  21. 2026-10-17 19:41 UTCEG score recompute
  22. 2026-10-17 19:41 UTCGHSA enrichmentGHSA-x69j-rqv7-gx25 · GitHub severity HIGH
  23. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  25. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
Show 32 more
  1. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-10-12 16:40 UTCEG score recompute
  4. 2026-10-12 03:49 UTCGHSA enrichmentGHSA-x69j-rqv7-gx25 · GitHub severity HIGH
  5. 2026-10-11 20:15 UTCEG score recompute
  6. 2026-10-11 16:50 UTCEG score recompute
  7. 2026-10-11 16:50 UTCGHSA enrichmentGHSA-x69j-rqv7-gx25 · GitHub severity HIGH
  8. 2026-10-11 15:01 UTCEG score recompute
  9. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  10. 2026-10-11 05:50 UTCEG score recompute
  11. 2026-10-11 05:50 UTCGHSA enrichmentGHSA-x69j-rqv7-gx25 · GitHub severity HIGH
  12. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  13. 2026-10-10 18:50 UTCGHSA enrichmentGHSA-x69j-rqv7-gx25 · GitHub severity HIGH
  14. 2026-10-10 07:51 UTCGHSA enrichmentGHSA-x69j-rqv7-gx25 · GitHub severity HIGH
  15. 2026-10-09 20:50 UTCEG score recompute
  16. 2026-10-09 20:50 UTCGHSA enrichmentGHSA-x69j-rqv7-gx25 · GitHub severity HIGH
  17. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  18. 2026-10-09 09:50 UTCGHSA enrichmentGHSA-x69j-rqv7-gx25 · GitHub severity HIGH
  19. 2026-10-08 22:48 UTCEG score recompute
  20. 2026-10-08 22:48 UTCGHSA enrichmentGHSA-x69j-rqv7-gx25 · GitHub severity HIGH
  21. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  22. 2026-10-08 11:49 UTCGHSA enrichmentGHSA-x69j-rqv7-gx25 · GitHub severity HIGH
  23. 2026-10-08 00:30 UTCEG score recompute
  24. 2026-10-08 00:30 UTCGHSA enrichmentGHSA-x69j-rqv7-gx25 · GitHub severity HIGH
  25. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  26. 2026-10-07 13:30 UTCGHSA enrichmentGHSA-x69j-rqv7-gx25 · GitHub severity HIGH
  27. 2026-10-07 02:27 UTCGHSA enrichmentGHSA-x69j-rqv7-gx25 · GitHub severity HIGH
  28. 2026-10-06 15:27 UTCGHSA enrichmentGHSA-x69j-rqv7-gx25 · GitHub severity HIGH
  29. 2026-10-06 11:27 UTCEG score recompute
  30. 2026-10-06 10:55 UTCEG score recompute
  31. 2026-10-06 10:45 UTCEG score recomputeFirst assessed: 7.5 HIGH
  32. 2026-10-06 10:44 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-103831?
CVE-2026-103831 is a high-severity vulnerability; its CVE record was published on October 6, 2026. 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…
When was CVE-2026-103831 made public?
CVE-2026-103831 was made public on October 6, 2026: that is the date its CVE record's CNA, Spanish National Cybersecurity Institute, S.A. (INCIBE), gives for when the vulnerability was made public. The CVE record itself was published on October 6, 2026. EchelonGraph's copy of the record carries a last-modified date of October 6, 2026; the record at its source may have been updated since.
Is CVE-2026-103831 actively exploited?
CVE-2026-103831 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-103831?
CVE-2026-103831 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-103831?
The CVE record's solution for CVE-2026-103831, written by its CNA Spanish National Cybersecurity Institute, S.A. (INCIBE), names the fix: "It is recommended to update the plugin to version 2.4.3 or later." The vendor advisories EchelonGraph has for CVE-2026-103831 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-103831

Explore →

Is Your Infrastructure Affected by CVE-2026-103831?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.