CVE-2026-71449

validatedZero produced an exploit or a check.

GHSA-w2h3-qvv9-248h ↗EUVD-2026-91069 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
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.
Johnson Controls EasyIO FS32 < 3.0b63
fixed in 3.0b63
CWE-321 Use of Hard-coded Cryptographic Key
ETK-2026-281, permanent identifier
+5h08mTTV
11mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
trigger signal (cve.org) +0hcheck available+5h08magent stopped
0
+1h
+2h
+3h
+4h

description

EasyIO FS32 versions earlier than 3.0b63 contain a hard-coded cryptographic key. An attacker may be able to obtain sensitive data embedded in affected devices; the required access conditions are not specified.

mitigation

Upgrade EasyIO FS32 to version 3.0b63 or later.

fixed in 3.0b63

check
available
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.30%20th percentile
agent run time
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-01 21: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 check: a technique exists and was validated, 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-01 21:16Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-281",
  "cve_id": "CVE-2026-71449",
  "display_id": "CVE-2026-71449",
  "ghsa_id": "GHSA-w2h3-qvv9-248h",
  "euvd_id": "EUVD-2026-91069",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Hard-coded cryptographic key in EasyIO FS32",
  "summary": "EasyIO FS32 versions earlier than 3.0b63 contain a hard-coded cryptographic key. An attacker may be able to obtain sensitive data embedded in affected devices; the required access conditions are not specified.",
  "mitigation": "Upgrade EasyIO FS32 to version 3.0b63 or later.",
  "vendor": "Johnson Controls",
  "product": "EasyIO FS32",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 3.0b63"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "3.0b63"
      ],
      "package_name": "EasyIO FS32",
      "purl": null
    }
  ],
  "cwes": [
    321
  ],
  "cvss_score": 10,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H",
  "epss_score": 0.003,
  "epss_percentile": 0.2087,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 10.793880616666666,
  "t0_at": "2026-10-01T21:16:57.610000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-02T02:25:06.490716+00:00",
      "days": 0.2139916749537037,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T21:16:57.610000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-01T21:16:57.610000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-01T21:16:57.610000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-71449"
    }
  }
}

published 2026-10-01 21:41Z
last change 2026-10-21 05:31Z

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.