CVE
matrix-hookshot denial of service in reply handling via unreadable parent
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
- Exploited
- No known exploitation
- Fix
- Fixed in 7.3.3
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. matrix-hookshot versions before 7.3.3 Bot receives a reply to an event it cannot read (M_NOT_FOUND)
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 15/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
matrix-hookshot, a Matrix bot for connecting to external services, can be crashed remotely by a user with low-privilege access. An attacker sends a crafted reply that points to a parent event the bot cannot read, which causes the service to shut down.
Written by a model from the sources below. Verify against them.
Original description
matrix-hookshot is a Matrix bot for connecting to external services like GitHub, GitLab, JIRA, and more. Prior to 7.3.3, Hookshot can crash in src/Bridge.ts while processing a modern Matrix reply whose m.relates_to.m.in_reply_to.event_id identifies an event that the bot cannot read. Bridge event handling calls botClient.getEvent() for the parent event without catching the resulting M_NOT_FOUND error, allowing the rejected request to escape reply processing and terminate the service. This issue is fixed in version 7.3.3.
Who should check
Teams running matrix-hookshot before 7.3.3 as a Matrix bridge to services such as GitHub, GitLab or JIRA.
“Hookshot, on versions < 7.3.3 , is vulnerable”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
matrix-hookshot versions before 7.3.3 Bot receives a reply to an event it cannot read (M_NOT_FOUND)Upgrade to a fixed version: 7.3.3.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-62267 (matrix-hookshot: Denial of service by replying to an event Hookshot can not read), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-62267 (entry last updated 2026-11-17):
Affected:
- matrix-org matrix-hookshot: fixed in 7.3.3
Fixed versions: 7.3.3.
Conditions (all must be true for the bug to be hit):
- matrix-hookshot versions before 7.3.3 (source: https://github.com/matrix-org/matrix-hookshot/security/advisories/GHSA-j286-3cjc-8f39)
- Bot receives a reply to an event it cannot read (M_NOT_FOUND) (source: https://github.com/matrix-org/matrix-hookshot/security/advisories/GHSA-j286-3cjc-8f39)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-62267 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-62267 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/matrix-org/matrix-hookshot/security/advisories/GHSA-j286-3cjc-8f39
- https://github.com/matrix-org/matrix-hookshot/pull/1258
- https://github.com/matrix-org/matrix-hookshot/commit/68ce0a116e6f6475dd9a69430cbc815068be6a20
- https://github.com/matrix-org/matrix-hookshot/releases/tag/7.3.3
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-62267
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-62267"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- matrix-org matrix-hookshot
fixed in 7.3.3
Evidence 6
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 3
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-62267
Is CVE-2026-62267 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A flaw in matrix-hookshot lets the service crash and terminate when it receives a reply to an event it cannot read, which returns an M_NOT_FOUND error. The result is a denial of service.Source: github.com
Which versions are affected by CVE-2026-62267?
matrix-hookshot: before 7.3.3.Source: cve.now feed data
Am I affected, and how do I check?
Versions of matrix-hookshot before 7.3.3 are affected, in the case where the bot receives a reply to an event it cannot read. To check a deployment, look at the installed matrix-hookshot version.Source: github.com
How do I fix CVE-2026-62267?
Upgrade matrix-hookshot to version 7.3.3 or later, which contains the fix.Source: github.com