CVE-2026-10629
Description
Verizon IMS SIP signaling lacks IPsec integrity protection, allowing on-path attackers to manipulate VoLTE signaling.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Verizon IMS SIP signaling lacks IPsec integrity protection, allowing on-path attackers to manipulate VoLTE signaling.
Vulnerability
The SIP signaling stack in Verizon's IMS network, in unspecified versions, implements SIP signaling without IPsec integrity protection. This is evidenced by the absence of Security-Client/Security-Server headers and ESP traffic, contrary to 3GPP TS 33.203 and GSMA IR.92 requirements [2].
Exploitation
An on-path attacker can exploit this vulnerability by passively monitoring and actively manipulating unsecured SIP messages over the radio and core network. This requires the attacker to be positioned between the user equipment and the IMS network to intercept and modify signaling traffic, such as registration, call setup, or messaging requests [2].
Impact
An attacker can compromise the confidentiality, integrity, and authenticity of VoLTE signaling. This manipulation could lead to denial of service, call redirection, or other unauthorized modifications to the signaling flow, affecting the integrity of voice and messaging services [2].
Mitigation
Verizon has stated that integrity support is "currently available at their request" and will be extended to all UEs "starting later this year." Apple's iOS 26.5 carrier bundle, released May 11, 2026, includes IMS IPsec-related configuration entries, suggesting device-side support may be enabled. However, network-level enforcement by Verizon has not yet been confirmed, and the vulnerability remains active for most users until this is observed [2].
AI Insight generated on Jun 2, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
2News mentions
0No linked articles in our index yet.