CVE-2026-108291

waiting for further signalsZero needs more public information before it can validate it.

GHSA-96vj-5338-hrmj ↗EUVD-2026-101017 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
itthinx Affiliates <= 7.0.1
CWE-502 Deserialization of Untrusted Data
ETK-2026-1571Zero's internal tracking ID, independent of the CVE number., permanent identifier
7d 06h 55msince last run
41mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+4h35m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

itthinx Affiliates versions through 7.0.1 are affected by unsafe deserialization that permits object injection. An attacker may be able to inject PHP objects through vulnerable deserialization handling; the advisory does not state any additional precondition.

mitigation

Update Affiliates to a version later than 7.0.1 if one is available from the maintainer. Until then, reduce exposure by disabling the plugin or restricting access to interfaces that process untrusted serialized data.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.46%38th percentile
agent run time
41m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-14 12:08Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-14 12:08Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-108291

{
  "etk_id": "ETK-2026-1571",
  "cve_id": "CVE-2026-108291",
  "display_id": "CVE-2026-108291",
  "ghsa_id": "GHSA-96vj-5338-hrmj",
  "euvd_id": "EUVD-2026-101017",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unsafe deserialization in itthinx Affiliates",
  "summary": "itthinx Affiliates versions through 7.0.1 are affected by unsafe deserialization that permits object injection. An attacker may be able to inject PHP objects through vulnerable deserialization handling; the advisory does not state any additional precondition.",
  "mitigation": "Update Affiliates to a version later than 7.0.1 if one is available from the maintainer. Until then, reduce exposure by disabling the plugin or restricting access to interfaces that process untrusted serialized data.",
  "vendor": "itthinx",
  "product": "Affiliates",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 7.0.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "affiliates",
      "purl": null
    }
  ],
  "cwes": [
    502
  ],
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0046,
  "epss_percentile": 0.3861,
  "epss_asof": "2026-10-21",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 41.29119705,
  "t0_at": "2026-10-14T12:08:28.433000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-14T12:08:28.433000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-14T12:08:28.433000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-108291"
    }
  }
}

published 2026-10-14 13:16Z
last change 2026-10-21 22:34Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.