Author: Sumit Chouhan, TMIET Published: April 2026
Read the full article: PDF →
Vehicular communication security was designed for a world where elliptic curve cryptography (ECC) was considered computationally secure for the foreseeable future. That assumption is now weakening with the emergence of quantum computing.
This repository presents a structured, implementation-aware approach to migrating V2X and VANET systems toward post-quantum cryptographic resilience covering standards, use cases, geographic boundaries, deployment architecture, technical challenges, and a phased roadmap grounded in what is actually achievable given today's hardware and protocol constraints.
| Factor | Reality |
|---|---|
| Vehicle service life | 12–20 years - well into the CRQC risk window |
| Current V2X security | IEEE 1609.2 and ETSI C-ITS both rely entirely on ECDSA P-256 |
| Quantum threat timeline | CRQC capability estimated 2029–2035 by national security agencies |
| Harvest now, decrypt later | Already an active threat model for long-lived V2X credentials |
| NIST PQC status | FIPS 203/204/205 finalized August 2024 — migration clock has started |
The full V2X security stack: IEEE 1609.2 (WAVE/DSRC), ETSI TS 103 097 (C-ITS), SAE J2945/1, 3GPP C-V2X, ISO/SAE 21434, and UNECE WP.29 and exactly where each standard is quantum-vulnerable.
How NIST's finalized algorithms map onto V2X requirements:
| Algorithm | FIPS | Replaces | V2X Role | Fit |
|---|---|---|---|---|
| ML-KEM (Kyber) | 203 | ECDH / ECIES | Session key establishment | ✅ Good |
| ML-DSA (Dilithium) | 204 | ECDSA | CA signing, OTA, V2I | |
| SLH-DSA (SPHINCS+) | 205 | ECDSA (CA only) | Root/Sub-CA only | |
| FN-DSA (FALCON) | 206* | ECDSA | V2V beaconing candidate | ✅ Best V2V fit |
Nine V2X use cases ranked by data sensitivity, message frequency, and consequence of compromise from PKI credential provisioning (Critical) to in-vehicle infotainment (Lower).
How PQC deployment scope should be defined by region - North America (NIST/SCMS), Europe (ETSI/CCMS), China/APAC (OSCCA/GB/T divergence), GCC/Middle East (greenfield opportunity), and the cross-border interoperability gap that no framework currently addresses.
Where PQC must be applied across the V2X stack - PKI/trust, message authentication, key exchange, bulk encryption, OTA updates, TLS backend, and HSM/OBU hardware - with migration difficulty rated for each.
Seven structural challenges that must be confronted:
- C1 : Latency vs. security overhead (10 ms V2V verification target)
- C2 : Certificate and message size inflation
- C3 : Hardware lifecycle and OBU constraints (ECC HSMs cannot be patched)
- C4 : SCMS/CCMS infrastructure migration complexity
- C5 : Regulatory and standards fragmentation (NIST, ETSI, 3GPP, SAE, OSCCA)
- C6 : Privacy preservation under larger PQC certificate models
- C7 : Algorithm maturity and side-channel risk on automotive hardware
Phase 1 (Now–2026) : Cryptographic inventory, SCMS planning, mandate PQC-capable HSMs in new OBU RFPs
Phase 2 (2026–2028) : PQC root/sub-CA deployment, OTA signing migrated to ML-DSA/SLH-DSA
Phase 3 (2028–2031) : Pseudonym certs: hybrid ECC + ML-DSA, V2I SPaT/MAP PQC at RSUs
Phase 4 (2031–2035) : V2V beaconing (BSM/CAM) PQC rollout as fleet threshold crossed
Phase 5 (Post-2035) : ECC deprecated per NIST IR 8547, full PQC-native fleet
Hybrid cryptography is the correct architectural approach not a temporary workaround.
Running ML-KEM alongside ECDH and ML-DSA alongside ECDSA during the transition provides security against both classical and quantum adversaries simultaneously. For long-lifecycle systems like vehicles, this is the only architecturally sound path.
Full PQC migration of V2V safety beaconing will not be complete before 2035.
The 10 Hz broadcast rate, 10 ms verification requirement, and constrained OBU hardware are hard physical constraints. Current PQC implementations do not meet them without dedicated hardware acceleration that does not yet exist in automotive-grade silicon at scale.
The governance gap is larger than the technical gap.
No single entity owns the SCMS or CCMS PQC root CA transition. Until a governance authority is defined for coordinating that migration, technical readiness is not enough.
Infrastructure first, always.
SCMS/CCMS, OTA signing pipelines, and V2C backend TLS are achievable now and represent the highest-value near-term targets.
| Layer | Status |
|---|---|
| Root/Sub-CA (SCMS/CCMS) | ✅ PQC migration viable now (ML-DSA / SLH-DSA) |
| OTA firmware signing | ✅ PQC migration viable now (ML-DSA) |
| V2C backend TLS | ✅ Hybrid ML-KEM + ECDH deployable now |
| V2I messages (SPaT/MAP) | |
| Pseudonym certificates | |
| V2V safety beaconing (BSM/CAM) | 🔴 ECC dominant through 2030+, hardware constraints unresolved |
| OBU hardware (HSM) | 🔴 New PQC-capable silicon required - mandate from 2026 in new RFPs |
-
Is the V2V beaconing problem actually solvable within real-time constraints?
Current research cannot consistently meet 10 ms verification at 10 Hz on automotive-grade embedded hardware without dedicated PQC accelerators. This is the central unresolved technical question. -
Who coordinates the SCMS root CA transition?
The SCMS/CCMS migration is a governance event, not just a technical one. No single authority currently owns it. -
Does geographic scoping create interoperability dead zones?
Divergent regional timelines will create certificate validation failures at borders without hybrid certificates and cross-domain trust agreements neither of which are standardised yet. -
Are NIST's general-purpose PQC algorithms right for V2X specifically?
ML-KEM and ML-DSA were designed as general-purpose algorithms. V2X is latency-critical, bandwidth-constrained, and hardware-limited. V2X-specific lightweight PQC variants remain in academic research, not standardised.
- Lightweight PQC variants specifically for V2V constrained environments
- PQC-aware pseudonym certificate format design (IEEE 1609.2 / ETSI TS 103 097 extensions)
- Automotive-grade PQC hardware acceleration benchmarking
- Cross-border trust model design and interoperability frameworks
- Integration with EV charging infrastructure (ISO 15118 / V2G ecosystems- a parallel and largely unaddressed PQC problem)
- Governance framework proposals for SCMS/CCMS PQC root CA transition
Key standards and research referenced in this work:
- NIST PQC Standardization Project - ML-KEM, ML-DSA, SLH-DSA, FN-DSA
- NIST FIPS 203 - ML-KEM specification
- NIST FIPS 204 - ML-DSA specification
- NIST FIPS 205 - SLH-DSA specification
- NIST IR 8547 - Transition timeline and deprecation schedule
- IEEE 1609.2-2022 - WAVE security services standard
- ETSI TS 103 097 - C-ITS security header and certificate formats
- ISO/SAE 21434:2021 - Road vehicles cybersecurity engineering
- AI-Driven PQC for V2X (arXiv 2025)
- Lightweight Key Agreement for V2X — Kyber+Saber (MDPI 2025)
- Adaptive PQC for 6G Vehicular Networks (arXiv 2026)
Full reference list with descriptions is included in the PDF article.
Content will be updated as standards and real-world deployments mature.