CVE-2026-109399

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

EUVD-2026-97496 ↗

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.
sbabic swupdate <= 2026.05.1
CWE-295 Improper Certificate Validation
ETK-2026-1375Zero's internal tracking ID, independent of the CVE number., permanent identifier
8d 12h 52msince last run
15mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+0h41m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

SWUpdate through 2026.05.1 can incorrectly accept CMS-signed updates because embedded certificates influence certificate-chain validation. An attacker with a signing key from another intermediate under the same trusted root could cause installation of a malicious update.

mitigation

Limit update ingestion to authenticated, trusted delivery paths and avoid installing update artifacts from untrusted sources. Where supported, pin acceptable signing certificates or intermediates and review trusted-root configuration; no fixed version is recorded.

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.
contextual
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.21%10th percentile
agent run time
15m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-12 15:16Z
Δ 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

Contextual: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-12 15:16Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1375",
  "cve_id": "CVE-2026-109399",
  "display_id": "CVE-2026-109399",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-97496",
  "status": "published",
  "anchor_state": "anchored",
  "title": "CMS certificate validation flaw in SWUpdate",
  "summary": "SWUpdate through 2026.05.1 can incorrectly accept CMS-signed updates because embedded certificates influence certificate-chain validation. An attacker with a signing key from another intermediate under the same trusted root could cause installation of a malicious update.",
  "mitigation": "Limit update ingestion to authenticated, trusted delivery paths and avoid installing update artifacts from untrusted sources. Where supported, pin acceptable signing certificates or intermediates and review trusted-root configuration; no fixed version is recorded.",
  "vendor": "sbabic",
  "product": "swupdate",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2026.05.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "swupdate",
      "purl": null
    }
  ],
  "cwes": [
    295
  ],
  "cvss_score": 9.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": 0.0021,
  "epss_percentile": 0.1057,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 14.774541133333333,
  "t0_at": "2026-10-12T15:16:44.440000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-12T15:16:44.440000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-12T15:16:44.440000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-109399"
    }
  }
}

published 2026-10-12 15:42Z
last change 2026-10-21 04:45Z

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.