No. TLS 1.2 is not quantum safe. It supports RSA key exchange (no forward secrecy) and ECDHE (Shor-vulnerable). TLS 1.2 also permits weaker cipher suites that TLS 1.3 removed.
Key Takeaway: TLS 1.2 is NOT quantum safe. Upgrade to TLS 1.3 with hybrid PQC key exchange. If TLS 1.2 must remain for compatibility, disable RSA key exchange and enforce ECDHE suites only.
TLS 1.2 is NOT quantum safe and has classical weaknesses.
TLS 1.2 (RFC 5246), published in 2008, was the dominant secure transport protocol until TLS 1.3's release in 2018. Unlike TLS 1.3 which mandates forward secrecy, TLS 1.2 supports both RSA key transport (no forward secrecy) and ephemeral Diffie-Hellman (DHE/ECDHE with forward secrecy). This flexibility creates security risks because misconfigurations can enable weak cipher suites.
In RSA key transport mode, the client generates a random session key, encrypts it with the server's public RSA key, and sends it to the server. The server decrypts using its private key, and both parties use the session key for symmetric encryption (AES). This provides no forward secrecy — if the server's private key is compromised in the future (or quantum-broken), all past sessions can be decrypted.
TLS 1.2 permits legacy cipher suites and negotiation choices that TLS 1.3 removed. The actual classical risk depends on the offered suites, selected suite, protocol extensions, implementation, and endpoint configuration; it must be measured.
TLS 1.2 faces multiple quantum vulnerabilities:
RSA key transport: Widely used in older TLS 1.2 configurations (especially in enterprise environments prioritizing compatibility). An adversary harvesting encrypted sessions today can decrypt them with a future quantum computer by breaking the server's RSA key — no forward secrecy protection.
ECDHE key exchange: Even with forward secrecy (ECDHE cipher suites), the key exchange is Shor-vulnerable. Recorded ECDHE handshakes can be decrypted post-quantum, despite ephemeral keys providing classical forward secrecy.
Certificate signatures: Server certificates are typically signed with RSA-SHA256 or ECDSA-SHA256, both Shor-vulnerable. Quantum adversaries could forge certificates enabling MITM attacks.
Prefer TLS 1.3 where the compatibility and control context supports it, then evaluate an approved hybrid key-exchange profile for HNDL-sensitive paths:
TLS 1.3 transition: Verify both endpoints, the selected cipher and group, certificates, fallback path, and compatibility before changing production policy.
Evaluate hybrid key exchange: Where both endpoints support a defined TLS 1.3 hybrid group, test negotiation, downgrade behavior, middleboxes, telemetry, and rollback.
Certificate migration: Track the approved certificate and relying-party profiles for the deployment context. There is no universal commercial 2030 certificate deadline.
Legacy clients and integrations may constrain a path to TLS 1.2. Identify the exact client, server, library, certificate, selected suite, and data lifetime before assigning classical or HNDL risk.
Payment environments follow the applicable PCI DSS version, compensating-control process, product constraints, and acquirer requirements. A TLS version alone is neither a compliance determination nor a complete quantum-risk verdict.
Embedded devices can have long replacement cycles and constrained cryptographic libraries. Record firmware updateability, protocol configuration, trust anchors, and supported profiles as evidence rather than assuming a fixed lifetime.
Prefer TLS 1.3 where the exact compatibility and control context supports it. For HNDL-sensitive paths, evaluate an approved hybrid profile through representative interoperability, downgrade, observability, and rollback testing.
| Full Name | Transport Layer Security 1.2 |
| Category | protocol |
| Quantum Vulnerability | RSA key transport (no forward secrecy, Shor-vulnerable). ECDHE (Shor-vulnerable). Weak cipher suites permitted. |
| NIST Status | TLS 1.2 remains a defined protocol, but acceptability depends on configuration and the applicable control profile. This page does not make a compliance determination. |
| Deprecation Timeline | No universal 2030 cutoff. Verify the governing profile and current endpoint support; NIST IR 8547 (final, October 2026) is NIST guidance, not a commercial mandate. |
| Replaced By | TLS 1.3 with hybrid PQC key exchange |
Protocol-level classification. A protocol version does not prove the algorithms, certificates, negotiation, downgrade behavior, or implementation used on a deployed path. Measure the endpoints before assigning coverage.
Evidence-scope review: 2026-07-10
Upgrade to TLS 1.3 with hybrid PQC key exchange. If TLS 1.2 must remain for compatibility, disable RSA key exchange and enforce ECDHE suites only.
QScout discovers instances of TLS 1.2 across your infrastructure within the approved engagement window — designed to minimize operational disruption. First-findings timing is set during operator scoping.