CVE-2026-112352

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

GHSA-rvgw-426x-67hr ↗EUVD-2026-111360 ↗

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.
Sunhillo Corporation SureLine >= 8.0.0, < 9.1.5
fixed in 9.1.5
ETK-2026-2802Zero's internal tracking ID, independent of the CVE number., permanent identifier
2h 47msince last run
14mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+3h06m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Sunhillo SureLine versions before 9.1.5 are affected by an authentication bypass in web-session handling. A remote unauthenticated attacker may impersonate a user with an active session and could obtain root-level command execution; exposure requires access to the affected web interface.

mitigation

Upgrade Sunhillo SureLine to version 9.1.5 or later. Restrict access to its web interface to trusted administrative networks until the upgrade is complete.

fixed in 9.1.5

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.
–
agent run time
14m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-27 19:43Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-10-27 19:43Z
    ghsa: trigger signal, started the run
  2. 2026-10-27 19:43Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2802",
  "cve_id": "CVE-2026-112352",
  "display_id": "CVE-2026-112352",
  "ghsa_id": "GHSA-rvgw-426x-67hr",
  "euvd_id": "EUVD-2026-111360",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in Sunhillo SureLine session handling",
  "summary": "Sunhillo SureLine versions before 9.1.5 are affected by an authentication bypass in web-session handling. A remote unauthenticated attacker may impersonate a user with an active session and could obtain root-level command execution; exposure requires access to the affected web interface.",
  "mitigation": "Upgrade Sunhillo SureLine to version 9.1.5 or later. Restrict access to its web interface to trusted administrative networks until the upgrade is complete.",
  "vendor": "Sunhillo Corporation",
  "product": "SureLine",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 8.0.0, < 9.1.5"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "9.1.5"
      ],
      "package_name": "SureLine",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 13.73727425,
  "t0_at": "2026-10-27T19:43:34.052000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-27T19:43:34.052000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-27T19:43:34.052000+00:00",
      "url": "https://github.com/advisories/GHSA-rvgw-426x-67hr"
    }
  }
}

published 2026-10-27 22:35Z
last change 2026-10-28 01:26Z

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.