Vulnerabilities

Vulnerability · RUSTSEC-2026-0336

MIKEY message MAC is never verified on receive, so forged messages are accepted

Published Oct 9, 2026 · RustSec Rust

Open the advisory

Exploitation likelihood is not on this record for RUSTSEC-2026-0336. A missing EPSS score is not a low risk. Compare RustSec Rust with the linked advisory before you change production.

Gaps on this record

  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
  • EPSS is missing. A missing score is not a low risk.
Severity
Unknown—
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
Awaiting synchronization with FIRST
Remediation
Not established
Affected products
RustSec Rust

implements MIKEY (RFC 3830) for SRTP key exchange. No receive path verified the MIKEY message authentication code. existed and was correct, but it was called only from unit tests — neither nor invoked it. computed an HMAC-SHA-1-160 over the serialized message and appended it, so the tag was present on the wire and looked like integrity protection. It was decorative: a receiver accepted any message regardless of whether the MAC was correct, wrong, or absent. ## Consequences - An attacker able to inject or modify MIKEY messages in transit faced no integrity check. Modified RAND, SSRC or security

No affected version ranges are stored yet. Use the vendor advisory before you decide this record does not apply.

How to fix RUSTSEC-2026-0336

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

Exploitation likelihood is not on this record for RUSTSEC-2026-0336. A missing EPSS score is not a low risk. Compare RustSec Rust with the linked advisory before you change production.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS is not on this record yet. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Oct 9, 2026 · RustSec Advisory DB

    Detected

    implements MIKEY (RFC 3830) for SRTP key exchange. No receive path verified the MIKEY message authentication code. existed and was correct, but it was called only from unit tests — neither nor invoked it. computed an HMAC-SHA-1-160 over the serialized message and appended it, so the tag was present on the wire and looked like integrity protection. It was decorative: a receiver accepted any message

Sources

  • RustSec Advisory DBVendor advisoryRUSTSEC-2026-0336

    implements MIKEY (RFC 3830) for SRTP key exchange. No receive path verified the MIKEY message authentication code. existed and was correct, but it was called only from unit tests — neither nor invoked it. computed an HMAC-SHA-1-160 over the serialized message and appended it, so

    crates.io

Freshness

Last verified in this catalog Unknown date. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.