When Quantum Advantage Becomes a Distraction
Last week I had two browser tabs open on the same monitor. One held the Digital Journal roundup of five quantum computing developments from May 2026, written in the now-familiar register of qubit counts climbing and milestones falling. The other tab was the CISA advisory list for the same week, where ABB had just shipped six separate bulletins. AC500 V2 PLCs leaking fragments of old Modbus telegrams. Terra AC wallboxes vulnerable to heap memory pollution that could rewrite firmware. Ability Camera Connect installing a years-old VLC 2.2.4 component. Zenon Remote Transport accepting unauthenticated OS reboot calls. LVS MConfig handing application secrets to anyone with local network access. The juxtaposition was hard to unsee.
Here is my position. The quantum advantage scorecard, as currently framed, has become the wrong axis to watch. Counting raw qubits and celebrating fidelity demos says very little about when the cryptographic horizon actually arrives, and almost nothing about whether the systems we need to protect will be ready when it does. The honest signal is buried inside measured benchmark studies on real workloads, not press releases. And the loud noise this month was not coming from a quantum lab. It was coming from a vendor of industrial controllers that still leaks Modbus state to whoever asks nicely.
The headline metric is not the cryptographic horizon
The five-developments framing keeps the conversation on the same axis it has been on since 2019. Qubit counts, gate fidelities, error correction milestones, and the occasional Random Circuit Sampling claim. These are real and they matter, but they are not what determines when a cryptographically relevant quantum computer becomes operational. That date is governed by overhead, and overhead is governed by the distance of the surface code you need to push physical errors down to a logical error budget small enough for Shor’s algorithm to finish.
A defensible estimate for breaking RSA-2048 with surface-code-protected Shor sits near 20 million physical qubits at current two-qubit gate error rates around 10^{-3}. The loudest 2026 announcements live two to three orders of magnitude below that. Atom Computing’s neutral-atom systems, IBM’s Condor and Fez generation, Quantinuum’s H2, Google’s Willow follow-on, all live in a hardware regime where logical qubit counts are measured in the low double digits at best.
So when an article frames five developments as steps on “the path to true quantum computing,” I want to know which axis those steps actually moved along. Did the surface-code distance budget improve. Did the magic state distillation overhead drop. Did anything happen that compresses the 20 million number. Usually the answer is no, and the framing remains the same.
The honest signal lives in measured benchmarks
Where the path is actually being walked is in benchmark work, not announcements. A recent IEEE Access study I worked on benchmarked 8-qubit ZZ feature-map quantum kernels on IBM’s 156-qubit ibm_fez processor against classical SVMs on industrial control datasets, reporting a statistically significant AUC improvement with p = 0.003 across cross-validated folds. The point is not that quantum kernels won. The point is that the win was small, measurable, reproducible, and tied to a real workload someone actually cares about. That is what a step on the path looks like in 2026. Modest, falsifiable, paid for in compute time on a public-access machine.
The Digital Journal roundup is full of language about “advantage” without specifying advantage over what, or under which assumed baseline. If a quantum demonstration cannot tell you the classical method it beat, the dataset it beat that method on, and the confidence interval, it is not a development on the path to true quantum computing. It is a development on the path to a press cycle.
ABB had a worse week than IBM had a good one
Look at what landed on CISA in the same window. ICSA-26–146–02 reports that AC500 V2 PLCs at firmware 2.5.2 and 2.5.3 expose fragments of earlier Modbus telegrams to an attacker who probes the right path. Modbus is the lingua franca of factory floors and substations. A device that leaks its prior session state leaks operational intent.
ICSA-26–146–01 covers Terra AC wallboxes, the EV charging product line. The advisory describes a heap pollution path that can take remote control of the unit and write to flash to alter firmware behavior. That is a route from a connected charger into persistent compromise of a grid-edge device. ICSA-26–146–05 reveals that Ability Camera Connect was shipped with VLC 2.2.4, a media player release from 2016, with the inherited vulnerabilities still in it. ICSA-26–146–03 lets an attacker trigger an unauthenticated OS reboot of the Zenon Remote Transport service. ICSA-26–146–06 sends LVS MConfig sensitive application data to anyone reachable on the local network.
None of those CVEs care about Shor’s algorithm. They are classical, present-tense, and exploit the same kinds of memory-handling and authentication failures that the ICS field has been writing post-mortems about for fifteen years. The grid-edge attack surface that needs to be migrated to post-quantum cryptography is the same surface that still ships VLC 2.2.4 in 2026.
Get Shujaatali Badami’s stories in your inbox
Join Medium for free to get updates from this writer.
This is what I mean by watching the wrong race. The harvest-now-decrypt-later threat assumes that adversaries are recording today’s encrypted traffic to break it later. The bigger problem is that today’s encrypted traffic is often not the most useful thing to record, because the same devices are bleeding plaintext through bugs that have nothing to do with cryptography. The PQ migration matters, and the IETF LAKE PQ-EDHOC work going on now is the right kind of plumbing, but it sits on top of devices that need to stop leaking state before they need to stop using ECDH.
A picture of the gap
The lower path produces material for the same adversary, sooner, with less ceremony. The upper path is the one we keep counting qubits about. A serious quantum-IoT security program plans for both, but it does not pretend the upper path is the only one going somewhere.
The numbers, side by side
Here is the comparison I keep on a sticky note next to the monitor.
Two halves of the same table. The top half is the path the headlines watch. The bottom half is the path the adversary already walks.
The math nobody wants to put on a slide
The reason qubit counts do not predict the cryptographically relevant horizon is that the surface code overhead grows fast in the code distance d, which itself grows with the target logical error rate p_L. A useful rough form is:
with p the physical two-qubit error rate, p_{\text{th}} the surface-code threshold near 10^{-2}, and N_{\text{log}} the count of logical qubits Shor needs. Plug in p = 3 \times 10^{-3}, p_{\text{th}} = 10^{-2}, N_{\text{log}} \approx 6000, p_L \approx 10^{-15}, and you land near the 20 million physical qubit figure. Pushing p down by a factor of three roughly halves d and quarters N_{\text{phys}}. Pushing qubit count up without pushing p down does almost nothing useful for an attacker holding ciphertext.
This is why the development that would actually move the cryptographic horizon is a two-qubit gate error rate sustained at 5 \times 10^{-4} across a connected lattice of thousands of qubits, not a press release about ten thousand physical qubits at 10^{-3}. The roundup almost never frames a milestone this way, because the audience is not asked to.
What I would put on the path instead
If I were writing a roundup of five developments for May 2026, three of the five would be about gate error rates published in peer-reviewed venues, one would be about logical error suppression scaling experiments on a code distance you can verify, and the fifth would be about the lifecycle of a PQ-EDHOC implementation running on a constrained controller in a substation. None of those make a headline. All of them shift the date when this stops being a thought experiment.
For the ICS side, the development I want listed every month is the count of devices in the field whose key-establishment stacks have moved to ML-KEM and whose firmware update paths are signed with ML-DSA or SLH-DSA. That is the metric that closes the harvest-now window for a substation. The PQ migration is going to happen one device family at a time, by people who have to keep the lights on while they do it. Counting qubits at Quantinuum does not move that number.
Back to the two browser tabs
So I sat there with the quantum advantage roundup on one side and the ABB advisory page on the other. Both tabs were dated within the same calendar week. One was telling me that we are walking faster on the path to true quantum computing. The other was telling me that the floors we are walking on still have holes in them. The honest read of May 2026 is that the quantum hardware story moved a little, the quantum software benchmarking story moved a little more, and the industrial control story moved sideways. The race the headlines describe is real. The race that decides whether the grid still works in 2032 is being run on a different track entirely, and the runners on that track are not the ones getting the photo.
The five-developments framing is fine as long as you remember to keep the second tab open.
