CVE-2026-123158

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

GHSA-4fcc-vm97-gx3x ↗EUVD-2026-117552 ↗

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.
OpenBSD OpenSSH < 10.6p2
fixed in 10.6p2
CWE-394 Unexpected Status Code or Return Value
ETK-2026-3644Zero's internal tracking ID, independent of the CVE number., permanent identifier
4h 27msince last run
21mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h51m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

OpenSSH sshd versions before 10.6p2 are affected on Linux hosts that use musl libc without PAM. On susceptible account configurations, a remote attacker may authenticate through password login without providing the account's correct password.

mitigation

Upgrade OpenSSH to version 10.6p2 or later. Prioritize musl-based Linux hosts without PAM; if an upgrade must wait, disable password authentication or enable PAM where feasible.

fixed in 10.6p2

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
21m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-05 15:46Z
Δ 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-11-05 15:46Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3644",
  "cve_id": "CVE-2026-123158",
  "display_id": "CVE-2026-123158",
  "ghsa_id": "GHSA-4fcc-vm97-gx3x",
  "euvd_id": "EUVD-2026-117552",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in OpenSSH sshd password handling",
  "summary": "OpenSSH sshd versions before 10.6p2 are affected on Linux hosts that use musl libc without PAM. On susceptible account configurations, a remote attacker may authenticate through password login without providing the account's correct password.",
  "mitigation": "Upgrade OpenSSH to version 10.6p2 or later. Prioritize musl-based Linux hosts without PAM; if an upgrade must wait, disable password authentication or enable PAM where feasible.",
  "vendor": "OpenBSD",
  "product": "OpenSSH",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 10.6p2"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "10.6p2"
      ],
      "package_name": "OpenSSH",
      "purl": null
    }
  ],
  "cwes": [
    394
  ],
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 20.660683233333334,
  "t0_at": "2026-11-05T15:46:26.488000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-05T15:46:26.488000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-05T15:46:26.488000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-123158"
    }
  }
}

published 2026-11-05 16:16Z
last change 2026-11-05 20:57Z

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.