A vehicle equipped for V2X (vehicle-to-everything) communication broadcasts its position, speed, and intent to other vehicles and infrastructure approximately ten times per second. Other vehicles, roadside units, and traffic infrastructure receive these messages and use them for safety applications including forward collision warning, intersection movement assist, and emergency vehicle approach notification. Each message is cryptographically signed so receivers can verify authenticity. The IEEE 1609.2 standard specifies the security profile and the supporting Security Credential Management System (SCMS). The European ETSI ITS-G5 stack uses similar but distinct profiles. Cellular V2X (C-V2X) defined in 3GPP releases 14 through 17 builds on this foundation. Quantum computers will eventually break the ECDSA signatures these systems rely on, and the migration to post-quantum signatures faces a unique challenge: signing rates of 10+ messages per second per vehicle, signature sizes that fit inside congested wireless channels, and certification timelines that span automotive product lifecycles.
This article walks through the V2X cryptographic stack, the IEEE 1609.2 SCMS architecture, the impact of post-quantum signature sizes on V2X communication, and how the standards bodies and OEMs are approaching this transition.
Why V2X Cryptography Has Unusual Constraints
V2X has a tighter cryptographic envelope than almost any other application. Each vehicle broadcasts Basic Safety Messages (BSM in the U.S.) or Cooperative Awareness Messages (CAM in Europe) at 10 Hz. A roadway with 1,000 vehicles in a several-kilometer radius generates 10,000 messages per second on the shared 5.9 GHz channel. Each message is signed and includes a certificate, which contributes substantially to the message size. The bandwidth budget is tight, and any signature size increase has direct congestion impact.
Today's V2X stacks use ECDSA P-256 signatures of 64 bytes (or 72 bytes encoded), with certificates that further inflate the bytes per message. The post-quantum signature schemes in NIST FIPS 204 are larger: ML-DSA-65 signatures are 3,309 bytes, ML-DSA-87 signatures are 4,627 bytes. SLH-DSA signatures are 7,856 to 49,856 bytes depending on parameters. None of these fit easily into the V2X bandwidth envelope as a drop-in replacement for ECDSA.
This is the engineering challenge that V2X PQC migration must solve. Approaches under consideration include compressed certificates, signature aggregation across multiple messages, and selective signing where not every message carries a full signature. The IEEE 1609 working group and the ETSI ITS technical committee are both engaged on the problem, with research contributions from academic and industry labs.
For broader background see What Is Post-Quantum Cryptography and Why RSA-2048 Will Break.
IEEE 1609.2 and the Security Credential Management System
IEEE 1609.2 specifies the security services for V2X applications based on Wireless Access in Vehicular Environments (WAVE). The standard defines certificate formats, signature algorithms, and message security headers. The supporting infrastructure is the Security Credential Management System, which provides pseudonym certificates to vehicles to support privacy while enabling authenticity.
The SCMS architecture includes several components: a Root Certificate Authority that anchors trust, an Intermediate Certificate Authority, an Enrollment Certificate Authority that provides long-term enrollment certificates, a Pseudonym Certificate Authority that provides short-term pseudonym certificates, a Linkage Authority that allows misbehavior detection without breaking pseudonymity in normal operation, and a Misbehavior Authority that handles revocation. The architecture is sophisticated and reflects the privacy-preserving requirements of V2X.
For PQC, the SCMS migration is multi-faceted. The Root CA and Intermediate CA need post-quantum signing keys. The Pseudonym CA needs to sign large numbers of pseudonym certificates with post-quantum algorithms. The vehicles need to verify post-quantum certificate chains during message reception. Each component has its own engineering challenges.
ETSI ITS-G5 and the European Approach
ETSI ITS-G5 is the European standard for V2X communication, with a different but related security profile from IEEE 1609.2. ETSI EN 302 663 specifies the access layer, ETSI TS 103 097 specifies the security profile, and ETSI TS 102 940 specifies the certificate management. The European approach has converged with the U.S. approach on many cryptographic and privacy details, with ongoing work on harmonization.
PQC migration in ITS-G5 follows the same engineering challenges as IEEE 1609.2. ETSI Technical Committee ITS has work items on post-quantum cryptography and is coordinating with IEEE 1609 on the technical approaches. The European Commission's Cooperative ITS deployment plans include cybersecurity considerations that increasingly address quantum risk.
For broader regulatory context see PQC for Government and Defense and the NIST FIPS Guide.
Cellular V2X and 3GPP Releases
Cellular V2X (C-V2X) provides V2X communication using cellular sidelink (PC5) and uplink/downlink (Uu) interfaces. 3GPP Release 14 introduced PC5 sidelink for V2X. Release 16 added enhanced V2X capabilities including platooning and cooperative driving. Release 17 introduced sidelink relay and improved positioning.
C-V2X security uses the cellular security stack on the Uu interface and extends IEEE 1609.2 / ETSI TS 103 097 on the PC5 interface. The PQC migration for C-V2X therefore includes both the cellular security migration (driven by 3GPP) and the PC5 sidelink security migration (driven by IEEE 1609 and ETSI TC ITS).
3GPP has work programs on post-quantum cryptography for 5G and beyond. The integration with V2X security profiles will be coordinated across the standards bodies.
Signing Rate and Verification Rate Realities
A vehicle broadcasts 10 BSMs per second. A receiving vehicle in a busy environment may need to verify hundreds or thousands of incoming BSMs per second, given that there are multiple vehicles in range each broadcasting at 10 Hz. ECDSA P-256 verification takes microseconds on modern automotive hardware. ML-DSA verification is slower but still feasible: ML-DSA-65 verification on a modern processor is in the low milliseconds. Aggregated verification across many messages can amortize costs.
The harder problem is signing. Every vehicle must sign 10 BSMs per second. ML-DSA signing is fast enough on automotive hardware, but the cumulative load matters when there are tens of millions of vehicles in a country and hundreds of millions globally. The hardware security modules in vehicle telematics units need to support post-quantum signing at scale. Vendor roadmaps for automotive HSMs are addressing this.
For migration construction details see Hybrid Encryption.
Pseudonym Certificate Issuance at Scale
The SCMS issues many pseudonym certificates per vehicle to support privacy. A typical configuration provisions 20 to 100 pseudonym certificates per vehicle per week, with rotation to prevent long-term tracking. Across a national vehicle fleet, this means billions of pseudonym certificates per week, each cryptographically signed.
For PQC migration, the Pseudonym CA needs to scale post-quantum signing operations to billions per week. The compute requirements are substantial but feasible with modern hardware. The bandwidth and storage for distributing pseudonym certificates is more challenging given the larger PQC certificate sizes. The migration engineering needs to address both the signing scale and the distribution infrastructure.
Hybrid Approaches and Profile Optimization
The V2X standards community is exploring several approaches to fit PQC into the V2X envelope. Hybrid signatures combining ECDSA with ML-DSA preserve backward compatibility while gaining post-quantum protection. Profile optimization including compressed certificates, certificate caching, and selective signature inclusion can reduce bandwidth impact. Algorithm selection within the PQC family, including consideration of compact post-quantum signature schemes that may emerge from ongoing research, can improve the size envelope.
The work is ongoing. SAE International, ISO TC 22, IEEE 1609, ETSI TC ITS, and 3GPP are all engaged in coordinated work on V2X PQC. The timeline for production deployment of PQC in V2X is the second half of the 2020s into the 2030s, with the migration following the natural vehicle replacement cycle.
Vehicle Lifecycle and Deployment Reality
Modern vehicles have a 15 to 20 year service life. Vehicles produced in 2030 will be on the road into the 2050s. The cryptographic stack in those vehicles needs to function across that window. Vehicles produced today with V2X capability will need PQC migration through OTA software updates and through hardware refresh during the vehicle's life. Some PQC migration may not be feasible in older vehicles, leading to a mixed-fleet operating environment where new and old vehicles coexist with different cryptographic capabilities.
Backward compatibility is therefore important. The migration approach should accommodate vehicles that can only do classical ECDSA alongside vehicles that can do hybrid PQC. The trust framework needs to handle both cases without breaking interoperability. SCMS protocol evolution should preserve mixed-fleet operation across the migration window.
For sector context see PQC for Critical Infrastructure Grid.
OEM and Tier 1 Supplier Considerations
V2X cryptographic stacks are typically delivered by Tier 1 suppliers (Bosch, Continental, Aptiv, Denso, Harman, Qualcomm, Marvell) integrating chipsets and HSMs from semiconductor vendors. The PQC migration in V2X depends on these suppliers delivering PQC-capable products to OEMs.
OEM procurement specifications for V2X subsystems should require PQC migration roadmaps from Tier 1 suppliers. Hardware security modules supporting ML-DSA at automotive grade need to be available, and the supply chain for these components needs to scale to global vehicle production volumes. The OEM-supplier coordination on PQC is a multi-year program.
ISO/SAE 21434 and Automotive Cybersecurity Engineering
ISO/SAE 21434 ("Road vehicles - Cybersecurity engineering") establishes the framework for cybersecurity in the automotive product lifecycle. The standard, which became effective in 2021, requires cybersecurity processes to be integrated from concept through development, production, operation, and decommissioning. UN Regulation No. 155 (UNECE WP.29) further requires cybersecurity management systems for vehicles sold in many global markets.
For PQC, ISO/SAE 21434 and UN R155 mean that the cryptographic posture of vehicles is not just an engineering choice but a regulated artifact subject to audit and type approval. OEMs need to document their cryptographic refresh plans, including PQC migration, as part of their cybersecurity management system. Type approval bodies are likely to begin asking about PQC roadmaps as the regulatory environment matures.
The interaction between automotive cybersecurity regulation and V2X-specific standards is an active coordination challenge. The same vehicle is subject to type approval requirements, V2X interoperability requirements, and automotive functional safety requirements (ISO 26262). PQC migration needs to satisfy all three regimes simultaneously, which requires coordinated planning across the OEM, the Tier 1 supplier, and the relevant standards bodies.
Frequently Asked Questions
Why is V2X PQC harder than enterprise IT PQC?
Three factors: signing rate (10 messages per second per vehicle), bandwidth constraints (busy 5.9 GHz channels with thousands of vehicles), and the SCMS pseudonym certificate volume (billions per week at fleet scale). All three drive engineering work that does not have direct enterprise IT analogs.
Will PQC signatures fit in V2X messages?
Not as a drop-in replacement. ML-DSA-65 signatures are 3,309 bytes versus 64 bytes for ECDSA. The standards community is working on profile optimization, compressed certificates, hybrid signatures, and selective signing to fit PQC into the V2X envelope. The work is ongoing and will be reflected in updated IEEE 1609.2 and ETSI TS 103 097 profiles.
What is the timeline for V2X PQC deployment?
Standards work is ongoing through the second half of the 2020s. Production deployment will follow the natural vehicle replacement cycle, with mixed-fleet operation across the migration window. Full fleet PQC capability is likely a 2040s outcome.
Are existing V2X-equipped vehicles upgradable?
Some are, through OTA software updates and HSM firmware updates. Some are not, due to chipset constraints in older Tier 1 components. The migration approach assumes mixed-fleet operation rather than flag-day cutover.
Does the U.S. or EU require post-quantum V2X?
Not yet by name as of 2026. The regulatory framework is evolving. The Department of Transportation's Federal Motor Vehicle Safety Standards do not address V2X cryptography directly. The European Commission's Cooperative ITS framework is moving toward including PQC requirements. The work in IEEE 1609 and ETSI TC ITS will inform regulatory expectations.
Sources
- IEEE. "IEEE 1609.2: Standard for Wireless Access in Vehicular Environments (WAVE) - Security Services." ieee.org.
- ETSI. "ETSI TS 103 097: Intelligent Transport Systems (ITS); Security; Security header and certificate formats." etsi.org.
- 3GPP. "TS 23.287: Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services." 3gpp.org.
- NIST. "FIPS 204: Module-Lattice-Based Digital Signature." nist.gov.
- NIST. "NIST IR 8547: Transition to Post-Quantum Cryptography Standards." nist.gov.
- USDOT. "ITS Joint Program Office Connected Vehicle Pilot Deployment." its.dot.gov.
- SAE International. "J3161/1: Cellular V2X (C-V2X) Standards." sae.org.
Related Articles
- What Is Post-Quantum Cryptography
- Why RSA-2048 Will Break
- Harvest Now, Decrypt Later
- PQC for Critical Infrastructure Grid
- Hybrid Encryption
Protect Your Data Before Q-Day Arrives
QNSQY's NIST-standardized post-quantum encryption protects files against both current and quantum-era threats.