Ruma identifiers validation: Validating Matrix Content URIs may panic
Affects ruma-identifiers-validationSource GCVE Database
Rated Medium by Threat Radar's AI analysis
- Patch
- Available – fixed in 0.13.0
Data as of 22 Nov 2026, 10:39 UTC
What to do
Upgrade ruma-identifiers-validation to 0.13.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
crates.ioruma-identifiers-validationpkg:cargo/ruma-identifiers-validationOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to ruma-identifiers-validation version 0.13.0 or later where this issue is fixed. The patch corrects the validation logic to properly handle server names up to the maximum length allowed by the Matrix specification.
Description
The ruma-identifiers-validation library contains a vulnerability where using the function mxc_uri::validate can cause a panic if the server name part of a Matrix Content URI exceeds 249 bytes. This occurs because the code assumes the server name length fits into a NonZeroU8 type, but the Matrix specification allows server names up to 261 bytes. This flaw was fixed in version 0.13.0.