CVE-2026-62267matrix-org matrix-hookshot uncaught exception
CVE-2026-62267 is a uncaught exception in matrix-org matrix-hookshot, rated high (7.1 on CVSS 4.0).
Why this priority: High severity, with no exploitation signal yet.
Published · Updated · NVD status: Received
What it is
An error nobody catches stops the process or request.
How it is reached
An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything.
What an attacker gains
A successful attack can take it offline. In practice, this kind of flaw lets an attacker exhaust CPU, memory or connections until the service stops answering.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- Upgrade matrix-org matrix-hookshot to 7.3.3 or later.
- Until it is patched, review who holds accounts that can reach it.
Description from NVD
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.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Public entry points and shared services that must stay up. The flaw sits between untrusted traffic and shared capacity.
Trust boundaries in play
- Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
- Between untrusted traffic and shared capacity. An attacker who crosses it can exhaust CPU, memory or connections until the service stops answering.
Questions to answer about your own systems
- Where does matrix-org matrix-hookshot run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Read more
Patches and commits
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.