CVE-2026-110104

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

GHSA-25gx-36j3-jw66 ↗EUVD-2026-98937 ↗

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.
xxyopen novel <= 3.5.0
CWE-916 Use of Password Hash With Insufficient Computational Effort
ETK-2026-1487Zero's internal tracking ID, independent of the CVE number., permanent identifier
7d 10h 50msince last run
52mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h03m
0
+4h
+6h
+8h
+10h
+12h

description

Xxyopen novel through 3.5.0 stores password verifiers as unsalted MD5 digests. An attacker who obtains the database password column through a leak or exposed backup may crack passwords offline and reuse recovered credentials.

mitigation

Restrict access to production databases and backup copies, and require password resets if password hashes may have been exposed. Replace unsalted MD5 password storage with a salted adaptive password-hashing scheme; 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.28%19th percentile
agent run time
52m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-13 16:53Z
Δ 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-13 16:53Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1487",
  "cve_id": "CVE-2026-110104",
  "display_id": "CVE-2026-110104",
  "ghsa_id": "GHSA-25gx-36j3-jw66",
  "euvd_id": "EUVD-2026-98937",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Weak password hashing in xxyopen novel",
  "summary": "Xxyopen novel through 3.5.0 stores password verifiers as unsalted MD5 digests. An attacker who obtains the database password column through a leak or exposed backup may crack passwords offline and reuse recovered credentials.",
  "mitigation": "Restrict access to production databases and backup copies, and require password resets if password hashes may have been exposed. Replace unsalted MD5 password storage with a salted adaptive password-hashing scheme; no fixed version is recorded.",
  "vendor": "xxyopen",
  "product": "novel",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 3.5.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "novel",
      "purl": null
    }
  ],
  "cwes": [
    916
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
  "epss_score": 0.0028,
  "epss_percentile": 0.1972,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 52.26983981666667,
  "t0_at": "2026-10-13T16:53:07.159000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-13T16:53:07.159000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-13T16:53:07.159000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-110104"
    }
  }
}

published 2026-10-13 18:04Z
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.