Skip to main content
VulnerabilityPublished

CVE-2026-62267: matrix-hookshot · Uncaught Exception

Affects matrix-hookshotSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.1 High : upgrade to 7.3.3 soon.

Data as of 17 Nov 2026, 18:37 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.07.1
Patch
Available – fixed in 7.3.3
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Upgrade matrix-hookshot to 7.3.3.

Affected software

ProductAffectedFixed in
matrix-orgmatrix-hookshotAffected
  • <7.3.3
Fixed in
  • 7.3.3

AI-suggested

Upgrade matrix-hookshot to version 7.3.3 or later, where the uncaught exception issue is fixed. No other mitigation is required as the fix addresses the root cause.

Description

matrix-hookshot versions prior to 7.3.3 contain an uncaught exception vulnerability in the Bridge.ts component. When processing a modern Matrix reply referencing an event that the bot cannot read, the botClient.getEvent() call throws an M_NOT_FOUND error that is not caught, causing the service to crash. This issue is resolved in version 7.3.3.

References

Community reviews

Loading reviews…