Google DeepMind cryptanalysis at a glance
Working with cryptographers Nadia Heninger and Emmanuel Thomé, Google DeepMind used AI agents on two problems in legacy 1024-bit RSA: forging signatures through signing interfaces, and factoring many keys at once. No deployed key was broken, and no keys were factored.
What changed with Google DeepMind cryptanalysis
On November 6, 2026, Pushmeet Kohli of Google DeepMind announced two working papers written with Nadia Heninger (UC San Diego and Inria) and Emmanuel Thomé (Inria). The first covers forging RSA signatures when an attacker can make a device, such as a hardware security module, sign data of their choosing billions of times. It proves that PKCS1 v1.5 padding adds no protection once the caller controls more than about half of the signed block, or a 64-byte digest at 1024 bits. Two cooperating AI agents then reran a known 1024-bit forgery on the test instance of an earlier academic study: the first root took 391 CPU core-years instead of 1,380, about 3.5 times less, in 3.2 days on up to 300,000 CPU cores and 16 GPUs. A human researcher sent about twenty short messages and wrote no code.
The second paper is theoretical. It gives each key in a batch its own family of number fields fed by shared precomputed work. At leading order, with a precomputation that costs one standard factoring run, each further 1024-bit key would cost about 1/58 of a run, 30 times less than the best earlier method for that budget, whose exponent had stood since 1993. No such factory has been built and no keys were factored; a two-agent AI system produced and checked the proofs, with the algebra machine-checked in Lean 4. The 1,600x figure in the announcement is also an estimate, for signers that take a 32-byte digest. Both papers say deployed RSA of 2048 bits or more is not threatened.
Google DeepMind cryptanalysis in numbers
Values are copied from the linked source on the date shown. They are not IA Compa measurements.
- CPU core-years for the first 1024-bit root (earlier study: 1,380)as of · Source for CPU core-years for the first 1024-bit root (earlier study: 1,380): storage.googleapis.com (opens in a new tab)
- 391 core-years
- Estimated cost cut per extra 1024-bit key vs MNFS (leading order)as of · Source for Estimated cost cut per extra 1024-bit key vs MNFS (leading order): storage.googleapis.com (opens in a new tab)
- 30x (estimate)
Why Google DeepMind cryptanalysis matters for businesses
NIST no longer approves 1024-bit RSA for creating signatures, but old keys linger in devices, certificates and signing services. Find where you still use 1024-bit RSA, including SSH keys, certificates and signing setups, and replace those keys with 2048-bit or larger ones. Don't let untrusted callers reach raw signing interfaces; signers that hash the data inside the device fall outside both attack models. Keep an inventory of where you use RSA, because the authors expect AI to keep speeding up this kind of research, and plan your move to stronger and post-quantum options well ahead of time.
Sources for this story
- Advancing the frontier of cryptanalysis (opens in a new tab)Official
Google DeepMind (Pushmeet Kohli) · x.com
- Two cryptographic advances on legacy 1024-bit RSA (opens in a new tab)Official
Google DeepMind (Pushmeet Kohli) · x.com
- Modular Roots from a Restricted Oracle: Faster Affine Roots and a 1024-bit Computation (working paper) (opens in a new tab)Official
Google DeepMind · storage.googleapis.com
- Fan Factories: Multiple Number Fields in Factorization Factories and Batch NFS (working paper) (opens in a new tab)Official
Google DeepMind · storage.googleapis.com
Last verified: . IA Compa summarizes public announcements for business readers. We are not affiliated with the companies mentioned. Always confirm details, pricing, and availability with the official source.
- #google-deepmind
- #cryptography
- #cryptanalysis
- #rsa
- #ai-agents
- #research

