Security
Reaction Attack on CKKS Deployments with Asymptotically Optimal Query Complexity
arXiv cs.CR0 views
arXiv:2610.21127v1 Announce Type: new Abstract: We study a protocol-level reaction leakage in CKKS deployments where public coefficient-to-slot (C2S) evaluation keys are combined with a client's 1-bit validity response. Under this deployment surface, a malicious evaluator can recover a ternary secret key using asymptotically optimal $O(H)$ reaction queries, where $H$ is the entropy of the secret key. The attack does not break RLWE or CKKS IND-CPA security. Instead, it exploits the interaction between client-side validity reactions and public homomorphic linear transformations. A shift of a public encryption key yields a ciphertext whose plaintext is a function of the secret key; the public ${\sf C2S}$ layer then repacks this information to construct a ciphertext whose validity depends strictly on whether a targeted secret coefficient matches a guessed value. Furthermore, each submitted query is independently randomized with a fresh encryption of zero, so that each resulting malicious ciphertext appears entirely distinct, thereby allowing the attack to simply evade trivial detection mechanisms on the client side. We implemented the full end-to-end attack in Lattigo v6.2.0 and recovered the full secret key across four parameter sets drawn from standard CKKS presets. For uniform ternary secrets, the attack uses $O(N)$ queries and is within a factor $2/\log_2 3 < 2$ of the oracle-only entropy lower bound. For sparse ternary secrets, a tailored variant further reduces the number of queries in practice. Our results show that observable validity reactions form a practical key-recovery channel in CKKS deployments exposing this surface, even when the underlying cryptographic assumptions remain intact.
Source:https://arxiv.org/abs/2610.21127PreviousApprove What, Exactly? Effect Binding and Trusted Rendering for Agent Step-Up AuthorizationNextStronger Judges Do Not See More: Deployment-Integrity Blindness in LLM Evaluation
Related posts
Testing and rebuilding Node.js snapshot artifacts after CVE-2026-106074
0dev.to Node
From predictable IDs to workflow risk: analyzing Node.js CVE-2026-106074
0dev.to Node
Upgrade planning for CVE-2026-106074 across Node.js 22, 24, and 26
0dev.to Node
I found 560 malware repos while building a GitHub trending site. GitHub removed them in a day
0dev.to OpenSource
PHP2Shell: The PHP Vulnerability Everyone Is Talking About Right Now (And How to Fix It)
0dev.to Security

HomeView could double as a HomeKit security camera, shows code
09to5Mac