CVE-2026-24084: Insecure Security Identifier Mechanism in Multi-Mode Call Processor
Published Aug 4, 2026
·Updated
Weak configuration when UE does not verify the consistency of its additional security capabilities with the replayed capabilities.
Event History
Aug 4, 2026
CVE Published
via MITRE·03:07 PM
Data Sourced
via MITRE·03:07 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:16 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2026-24084?
CVE-2026-24084 has a severity score of 7.5, classified as high.
2
What vulnerability does CVE-2026-24084 describe?
CVE-2026-24084 describes an insecure security identifier mechanism within a Multi-Mode Call Processor due to weak configuration.
3
How do I fix CVE-2026-24084?
To mitigate CVE-2026-24084, ensure that the User Equipment (UE) verifies the consistency of its additional security capabilities.
4
What are the risks associated with CVE-2026-24084?
The risks include potential unauthorized access and data compromise due to insecure handling of security identifiers.
5
Is there any workaround for CVE-2026-24084?
Currently, the most effective workaround for CVE-2026-24084 is to apply proper security capabilites verification in the UE.