matrix-org matrix-hookshot up to 7.3.2 Bridge src/Bridge.ts botClient.getEvent exceptional condition
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00+ |
Summary
A vulnerability, which was classified as problematic, has been found in matrix-org matrix-hookshot up to 7.3.2. Affected is the function botClient.getEvent of the file src/Bridge.ts of the component Bridge. The manipulation leads to exceptional condition.
This vulnerability is listed as CVE-2026-62267. The attack may be initiated remotely. There is no available exploit.
It is advisable to upgrade the affected component.
Details
A vulnerability was found in matrix-org matrix-hookshot up to 7.3.2. It has been rated as problematic. This issue affects the function botClient.getEvent of the file src/Bridge.ts of the component Bridge. The manipulation with an unknown input leads to a exceptional condition vulnerability. Using CWE to declare the problem leads to CWE-755. The product does not handle or incorrectly handles an exceptional condition. Impacted is availability. The summary by CVE is:
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.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-62267 since 07/13/2026. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available.
Upgrading to version 7.3.3 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Exceptional conditionCWE: CWE-755
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: matrix-hookshot 7.3.3
Timeline
07/13/2026 CVE reserved11/17/2026 Advisory disclosed
11/17/2026 VulDB entry created
11/17/2026 VulDB entry last update
Sources
Product: github.comAdvisory: github.com
Status: Confirmed
CNA: GitHub_M
CVE: CVE-2026-62267 (🔒)
GCVE (CVE): GCVE-0-2026-62267
GCVE (VulDB): GCVE-100-438173
Entry
Created: 11/17/2026 19:39Changes: 11/17/2026 19:39 (69)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.