nday
CVE-2026-77331 GHSA-72jh-722p-rqr3

memtomem-stm: Concurrent LTM recovery can duplicate reconnects or reuse a cancelled transport session

memtomem / memtomem-stm

Hay constancia de un parche 1 día después de la divulgación. Versión corregida: memtomem-stm 0.1.34. Ninguna de las cuatro fuentes de PoC la recoge. No figura en el KEV de CISA.

tags weakness typerace condition accesslocalno user interaction ecosystemPyPI
why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

race condition
CWE-362, stated by the CNA GitHub_M, NVD, republishing [email protected] y GitHub advisory GHSA-72jh-722p-rqr3
local
AV:L in CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:L (CVSS 4.0) from the CNA GitHub_M
no user interaction
UI:N in CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:L (CVSS 4.0) from the CNA GitHub_M
PyPI
GHSA-72jh-722p-rqr3: pip packages memtomem-stm
etapa
PAT
divulgación
divulgación → parche
T+1d
cvss
2.0 LOW v4.0

Ciclo de vida

Eje x en UTC; punto = minuto exacto, barra ancha = solo fecha, hueco = desconocida o inferida.
fecha desconocida
DISdivulgada
11-20T16:56Z
PATparcheada
11-21T00:03Z
ANAanalizada
sin registro aún
POCPoC
sin registro aún
ITWexplotada
sin registro aún
KEVen KEV
sin registro aún

Descripción

memtomem-stm is a short-term memory proxy gateway with proactive memory surfacing for AI agents. From 0.1.2 until 0.1.34, concurrent surfacing RPC failures can start more than one reconnect for the same dirty session because concurrent LTM recovery is not uniquely owned by a session generation. Cancellation during a post-reconnect retry can also leave the replacement transport reusable after an interrupted protocol exchange, causing session-state integrity loss or local service degradation. The duplicate-reconnect subcase was introduced in 0.1.24, while the cancellation-recovery subcase affects the broader listed range. This issue is fixed in version 0.1.34.

Original text of the CVE record (cvelist), shown as published.

Exploit conditions

What an attack needs, read from the CVSS vector.
Attack vector AV:L
Local: needs a local or SSH session, or a user tricked into acting on the machine
Attack complexity AC:H
High: the attacker must evade or get around security measures such as ASLR or DEP, or obtain target-specific secrets
Attack requirements AT:P
Present: success depends on specific deployment or execution conditions, such as a race condition, a non-default setting or a position on the network path
Privileges required PR:L
Low: ordinary user privileges
User interaction UI:N
None: no action by anyone other than the attacker

CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:L

CVSS 4.0 vector from the CVE record, scored by the CNA GitHub_M.

Registro de eventos

+DISdivulgación

GitHub_M publicó el registro CVE. CVSS 2, severidad baja.

fuente cvelist · nday , observado en tiempo real · en bruto
{
  "id": 497699,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2026-77331",
  "occurred_at": "2026-11-20T16:56:23.75Z",
  "observed_at": "2026-11-20T17:02:30.44668Z",
  "is_backfill": false,
  "dedupe_key": "",
  "detail": {
    "cvss": {
      "source": "cna",
      "vector": "CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:L",
      "version": "4.0",
      "base_score": 2,
      "base_severity": "LOW"
    },
    "ssvc": {
      "timestamp": "2026-11-20T19:21:34.035178Z",
      "automatable": "no",
      "exploitation": "none",
      "technical_impact": "partial"
    },
    "state": "PUBLISHED",
    "date_published": "2026-11-20T16:56:23.750Z",
    "assigner_short_name": "GitHub_M"
  }
}
hora observada en tiempo real por nday
+PATparche registrado

Versión corregida según el aviso: memtomem-stm 0.1.34. El aviso enlaza los commits de la corrección. Aviso publicado el ; no consta cuándo se publicó el parche en sí.

fuente ghsa GHSA-72jh-722p-rqr3 · nday , observado en tiempo real · en bruto
{
  "id": 498417,
  "type": "patch_released",
  "source": "ghsa",
  "url": "https://github.com/advisories/GHSA-72jh-722p-rqr3",
  "occurred_at": null,
  "observed_at": "2026-11-21T00:03:22.984947Z",
  "is_backfill": false,
  "dedupe_key": "GHSA-72jh-722p-rqr3",
  "detail": {
    "cvss": {
      "cvss_v3": {
        "score": 0.0,
        "vector_string": null
      },
      "cvss_v4": {
        "score": 2.0,
        "vector_string": "CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:L"
      }
    },
    "cwes": [
      {
        "name": "Concurrent Execution using Shared Resource with Improper Synchronization",
        "cwe_id": "CWE-362"
      }
    ],
    "ghsa_id": "GHSA-72jh-722p-rqr3",
    "packages": [
      {
        "name": "memtomem-stm",
        "ecosystem": "pip",
        "first_patched_version": "0.1.34",
        "vulnerable_version_range": ">= 0.1.2, <= 0.1.33"
      }
    ],
    "severity": "low",
    "references": [
      "https://github.com/memtomem/memtomem-stm/security/advisories/GHSA-72jh-722p-rqr3",
      "https://nvd.nist.gov/vuln/detail/CVE-2026-77331",
      "https://github.com/memtomem/memtomem-stm/commit/761db1802df7ce4881ff4c3acee6d674925da498",
      "https://github.com/memtomem/memtomem-stm/releases/tag/v0.1.34",
      "https://github.com/advisories/GHSA-72jh-722p-rqr3"
    ],
    "fix_commit_urls": [
      "https://github.com/memtomem/memtomem-stm/commit/761db1802df7ce4881ff4c3acee6d674925da498"
    ],
    "github_reviewed_at": "2026-11-20T23:38:15Z",
    "advisory_updated_at": "2026-11-20T23:38:16Z",
    "source_code_location": "https://github.com/memtomem/memtomem-stm",
    "advisory_published_at": "2026-11-20T23:38:15Z"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Debate de investigadores

0 investigadores lo mencionaron en los últimos 7 días

Publicaciones en X de investigadores de la lista de nday que mencionan este CVE, tal como se publicaron. nday no las verifica.

nday aún no ha recopilado publicaciones en X de investigadores de su lista sobre este CVE.

Discussion

0 comments

No comments yet.