CVE-2026-110679

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

GHSA-2444-rr4q-h72r ↗EUVD-2026-101677 ↗

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.
OpenSIPS 3.6.0; 3.6.1; 3.6.2; 3.6.3; 3.6.4; 3.6.5; 3.6.6; 3.6.7; 3.6.8; 4.0.0; 4.0.1
ETK-2026-1892Zero's internal tracking ID, independent of the CVE number., permanent identifier
3d 10h 10msince last run
1h 32mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+70h07m
0
+2h
+4h
+6h
+8h
+10h

description

OpenSIPS versions through 3.6.8 and 4.0.1 contain an out-of-bounds read in the rtpproxy module's offer and answer handling. A remote unauthenticated attacker may trigger the flaw by reaching the affected SIP processing path.

mitigation

Upgrade OpenSIPS 3.6 installations to 3.6.9 or later, and 4.0 installations to 4.0.2 or later. Restrict untrusted access to SIP processing endpoints until upgrades are 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.
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.31%22nd percentile
agent run time
1h 32m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-14 20:30Z
Δ 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-14 20:30Z
    ghsa: trigger signal, started the run
  2. 2026-10-14 20:30Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1892",
  "cve_id": "CVE-2026-110679",
  "display_id": "CVE-2026-110679",
  "ghsa_id": "GHSA-2444-rr4q-h72r",
  "euvd_id": "EUVD-2026-101677",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Out-of-bounds read in OpenSIPS rtpproxy",
  "summary": "OpenSIPS versions through 3.6.8 and 4.0.1 contain an out-of-bounds read in the rtpproxy module's offer and answer handling. A remote unauthenticated attacker may trigger the flaw by reaching the affected SIP processing path.",
  "mitigation": "Upgrade OpenSIPS 3.6 installations to 3.6.9 or later, and 4.0 installations to 4.0.2 or later. Restrict untrusted access to SIP processing endpoints until upgrades are complete.",
  "vendor": null,
  "product": "OpenSIPS",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "3.6.0",
        "3.6.1",
        "3.6.2",
        "3.6.3",
        "3.6.4",
        "3.6.5",
        "3.6.6",
        "3.6.7",
        "3.6.8",
        "4.0.0",
        "4.0.1"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "OpenSIPS",
      "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.0031,
  "epss_percentile": 0.2211,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 92.10605253333334,
  "t0_at": "2026-10-14T20:30:20.592000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-14T20:30:20.592000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-14T20:30:20.592000+00:00",
      "url": "https://github.com/advisories/GHSA-2444-rr4q-h72r"
    }
  }
}

published 2026-10-17 15:32Z
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.