Security readout for executives and security teams
Plain-English summary
Applications using gotd/td before 0.145.1 can be remotely forced to consume excessive memory before authentication. An attacker may cause slowdowns, crashes, or service restarts without credentials. The issue affects availability only; the supplied sources do not indicate data theft or modification.
Executive priority
Prioritize remediation for internet-facing or otherwise attacker-reachable services because exploitation requires no authentication and can interrupt availability. Upgrade promptly through normal emergency dependency procedures. Isolated development systems are lower priority, but vulnerable production artifacts should not remain deployed. No confidentiality or integrity impact is documented.
Technical view
proto.UnencryptedMessage.Decode trusts an attacker-controlled dataLen in an unauthenticated MTProto packet and allocates that amount before confirming sufficient buffered data. This can create excessive memory use and CPU or garbage-collection pressure. CVE-2026-54638 is rated CVSS 7.5 and maps to CWE-770 and CWE-789. Version 0.145.1 fixes the flaw.
Likely exposure
Exposure exists where software includes gotd/td below 0.145.1 and processes attacker-reachable, unencrypted MTProto traffic. Risk is greatest for continuously available services without strict network isolation or resource controls. The supplied sources provide no CPEs or deployment inventory, so each organization must identify affected dependencies and reachable processing paths.
Exploitation context
The attack is remote, unauthenticated, low complexity, and requires no user interaction. Its documented impact is denial of service through memory allocation and processing pressure. The source bundle marks this CVE as absent from KEV and provides no evidence of active exploitation; real-world exploitation status is therefore unconfirmed.
Researcher notes
The vulnerable operation occurs before remaining-buffer validation in proto/unencrypted_message.go. The supplied advisory, issue, patch commit, and release identify 0.145.1 as fixed. Assessment should focus on dependency reachability, actual packet-processing paths, and resource behavior. No exploit prevalence, affected downstream product list, or CPE mapping is provided.
Mitigation direction
- Upgrade gotd/td to version 0.145.1 or later.
- Rebuild and redeploy every application containing the vulnerable dependency.
- Until upgraded, restrict untrusted access to affected MTProto processing where operationally feasible.
- Apply memory limits and restart controls as temporary resilience measures, not substitutes for upgrading.
Validation and detection
- Inspect dependency manifests, lockfiles, SBOMs, and deployed binaries for gotd/td versions below 0.145.1.
- Confirm all production artifacts were rebuilt with gotd/td 0.145.1 or later.
- Identify whether untrusted networks can reach code processing unencrypted MTProto packets.
- Review monitoring for abnormal memory growth, garbage-collection pressure, crashes, or repeated restarts.
- Test safely that malformed length declarations are rejected without allocation proportional to the declared size.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-770: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-789: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-54638 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6GitHub_MVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/gotd/td/security/advisories/GHSA-whmm-qj9r-wvr2CVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/gotd/td/issues/1711CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/gotd/td/commit/9d5d1f31ea5022d9798d84ccce15de2e91ba6baaCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/gotd/td/releases/tag/v0.145.1CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Allocation of Resources Without Limits or Throttling
Allocation of Resources Without Limits or Throttling represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Memory Allocation with Excessive Size Value
Memory Allocation with Excessive Size Value represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.