惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

D
Docker
IT之家
IT之家
Microsoft Security Blog
Microsoft Security Blog
博客园 - 司徒正美
云风的 BLOG
云风的 BLOG
P
Proofpoint News Feed
D
DataBreaches.Net
B
Blog RSS Feed
博客园_首页
The GitHub Blog
The GitHub Blog
I
InfoQ
L
LangChain Blog
G
Google Developers Blog
M
MIT News - Artificial intelligence
美团技术团队
腾讯CDC
V
Visual Studio Blog
aimingoo的专栏
aimingoo的专栏
博客园 - 聂微东
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Apple Machine Learning Research
Apple Machine Learning Research
A
About on SuperTechFans
博客园 - 三生石上(FineUI控件)
博客园 - 叶小钗

CERT Recently Published Vulnerability Notes

CERT/CC Vulnerability Note VU#369611 CERT/CC Vulnerability Note VU#687587 CERT/CC Vulnerability Note VU#718077 CERT/CC Vulnerability Note VU#859658 CERT/CC Vulnerability Note VU#943094 CERT/CC Vulnerability Note VU#889462 CERT/CC Vulnerability Note VU#456290 CERT/CC Vulnerability Note VU#308749 CERT/CC Vulnerability Note VU#728712 CERT/CC Vulnerability Note VU#756733 CERT/CC Vulnerability Note VU#874418 CERT/CC Vulnerability Note VU#431093 CERT/CC Vulnerability Note VU#614868 CERT/CC Vulnerability Note VU#987105 CERT/CC Vulnerability Note VU#487613 CERT/CC Vulnerability Note VU#243636 CERT/CC Vulnerability Note VU#281278 CERT/CC Vulnerability Note VU#790363 CERT/CC Vulnerability Note VU#293714 CERT/CC Vulnerability Note VU#305509 CERT/CC Vulnerability Note VU#141367 CERT/CC Vulnerability Note VU#492466 CERT/CC Vulnerability Note VU#847406 CERT/CC Vulnerability Note VU#360868 CERT/CC Vulnerability Note VU#762226 CERT/CC Vulnerability Note VU#885548 CERT/CC Vulnerability Note VU#326070 CERT/CC Vulnerability Note VU#529388 CERT/CC Vulnerability Note VU#725167 CERT/CC Vulnerability Note VU#564823
CERT/CC Vulnerability Note VU#615987
2026-06-02 · via CERT Recently Published Vulnerability Notes

Overview

VoLTE deployments on Verizon’s IMS network have operated without negotiated SIP integrity protection. In observed test conditions, SIP signaling—including registration, call setup, and messaging—traveled without IPsec ESP encapsulation and without SIP Security Agreement headers, exposing it to interception and modification by on-path attackers.

Recent carrier configuration updates, including Apple’s iOS 26.5 carrier bundle released on May 11, 2026, include IMS IPsec–related settings. However, such configuration entries do not confirm active deployment, successful negotiation, or functional protection in production.

Description

CVE-2026-10629
Verizon IMS deployments were observed transmitting SIP signaling without integrity protection. REGISTER exchanges lacked Security-Client, Security-Server, and Security-Verify headers, and no ESP-encapsulated SIP traffic was detected during subsequent signaling such as INVITE, MESSAGE, BYE, and UPDATE. This pattern persisted across devices, operating systems, and network conditions, indicating a deliberate network configuration rather than a transient issue.

Per 3GPP TS 33.203 and GSMA IR.92, SIP signaling between the UE and P-CSCF must be protected using IPsec ESP following IMS AKA authentication, with negotiation occurring during registration. The absence of this protection allows attackers to manipulate SIP signaling undetected, enabling call hijacking, spoofing, denial-of-service, and misrouting of emergency calls.

Verizon initially acknowledged the issue and stated that integrity support would be available upon request and extended broadly later in the year. However, the company has since ceased participation in coordination, including follow-up discussions and draft review, and has not provided verifiable evidence of mitigation. As remediation remains unconfirmed, this disclosure proceeds to inform users of an ongoing security exposure.

Independent verification would require observation of successful SIP security negotiation, ESP-protected traffic, or official confirmation from Verizon.

Impact

Without integrity protection, on-path attackers can intercept, replay, or alter SIP messages with no risk of detection. This undermines core VoLTE security assumptions and enables signaling spoofing, call disruption, and manipulation of emergency routing.

Although recent configuration changes suggest potential progress, their operational status remains unverified. Until protections are confirmed, the risk persists.

Solution

Remediation requires coordinated network and device-side changes. Verizon must enable and enforce SIP security negotiation and ESP protection in its IMS core infrastructure, and devices must receive and apply correct carrier configuration to support IPsec.

Verification should confirm successful SIP security negotiation and ESP-protected signaling, either through observed headers, traffic capture, or operator confirmation.

Until then, organizations relying on high-assurance VoLTE should treat signaling as untrusted

Acknowledgements

The authors thank DongWon Lee, Jeongmin Choi, and CheolJun Park from Kyung Hee University for their technical analysis, coordination efforts, and identification of the iOS 26.5 configuration updates. Their work has advanced understanding of this issue and ensured disclosures remain grounded in observable evidence.
This report was prepared by Timur Snoke, with AI-assisted drafting to support clarity and accuracy.

Vendor Information

Filter by content: Additional information available

 Sort by: