CVE-2026-105486

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

GHSA-m55h-2fw5-fv4g ↗EUVD-2026-92916 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).+0mkevAttacks confirmed in the real world.
OSSRS srs 7.0-a1
ETK-2026-721, permanent identifier
14d 23h 56msince last run
36mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hpublic poc+0hwaiting for further signals+3h21m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

OSSRS srs versions through 7.0-a1 have an authentication bypass in the System API. A remote attacker may access affected API functionality without authentication when the System API is network-accessible.

mitigation

Upgrade OSSRS srs to version 8.0-d0 or later. Restrict network access to the System API until the upgrade is complete.

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.
–
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.50%41st percentile
agent run time
36m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-06 01:30Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+0m
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-10-06 01:30Z
    ghsa: trigger signal, started the run
  2. 2026-10-06 01:30Z
  3. 2026-10-11 23:37Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-721",
  "cve_id": "CVE-2026-105486",
  "display_id": "CVE-2026-105486",
  "ghsa_id": "GHSA-m55h-2fw5-fv4g",
  "euvd_id": "EUVD-2026-92916",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in OSSRS srs System API",
  "summary": "OSSRS srs versions through 7.0-a1 have an authentication bypass in the System API. A remote attacker may access affected API functionality without authentication when the System API is network-accessible.",
  "mitigation": "Upgrade OSSRS srs to version 8.0-d0 or later. Restrict network access to the System API until the upgrade is complete.",
  "vendor": "OSSRS",
  "product": "srs",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "7.0-a1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "srs",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.3,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L",
  "epss_score": 0.005,
  "epss_percentile": 0.4128,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 35.80986045,
  "t0_at": "2026-10-06T01:30:45.640000+00:00",
  "signals": {
    "public_poc": {
      "at": "2026-10-06T01:30:45.640000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-06T01:30:45.640000+00:00",
      "url": "https://github.com/ossrs/srs/issues/4690"
    },
    "trigger_signal": {
      "at": "2026-10-06T01:30:45.640000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-06T01:30:45.640000+00:00",
      "url": "https://github.com/advisories/GHSA-m55h-2fw5-fv4g"
    }
  }
}

published 2026-10-06 04:15Z
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.