CVE-2026-104591

waiting for further signals

EUVD-2026-110101 ↗

no check availablenot proven exploitable

cve.orgpublic pockev

libosmocore n/a

ETK-2026-2685, permanent identifier

1h 14msince last run

23mAI analysis

timeline

0 = trigger signal

trigger signal (cve.org) +0hwaiting for further signals+20h07m

+2h

+4h

+6h

+8h

+10h

description

libosmocore versions through 1.14.1 contain a buffer overflow in IUUP payload CRC handling. A remote attacker may be able to trigger a denial of service when they can send data to an application that reaches the affected processing path.

mitigation

Restrict untrusted remote access to services that process IUUP traffic and monitor them for unexpected termination. Apply a vendor-provided corrected libosmocore release when one is available; the evidence does not identify a fixed version.

check

exploit

automation

contextual

auth required

–

EPSS

–

agent run time

23m

cve.org record, t = 0

2026-10-26 00:00Z

Δ to public poc

–

Δ to kev

–

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.

2026-10-26 00:00Z
cve_org: trigger signal, started the run
https://www.cve.org/CVERecord?id=CVE-2026-104591

this entry in the feed

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

{
  "etk_id": "ETK-2026-2685",
  "cve_id": "CVE-2026-104591",
  "display_id": "CVE-2026-104591",
  "ghsa_id": null,
  "euvd_id": "EUVD-2026-110101",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Buffer overflow in libosmocore IUUP CRC processing",
  "summary": "libosmocore versions through 1.14.1 contain a buffer overflow in IUUP payload CRC handling. A remote attacker may be able to trigger a denial of service when they can send data to an application that reaches the affected processing path.",
  "mitigation": "Restrict untrusted remote access to services that process IUUP traffic and monitor them for unexpected termination. Apply a vendor-provided corrected libosmocore release when one is available; the evidence does not identify a fixed version.",
  "vendor": null,
  "product": "libosmocore",
  "affected": [
    {
      "affected_notes": [
        "n/a"
      ],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "n/a",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 22.832793766666665,
  "t0_at": "2026-10-26T00:00:00+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-26T00:00:00+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-26T00:00:00+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-104591"
    }
  }
}

published 2026-10-26 19:43Z
last change 2026-10-26 21:18Z

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.