# Malformed BinFHEContext archive can trigger a heap-buffer-overflow in RingGSWCryptoParams::PreCompute

**URL:** <https://openfhe.discourse.group/t/malformed-binfhecontext-archive-can-trigger-a-heap-buffer-overflow-in-ringgswcryptoparams-precompute/2352>\
**Category:** Bug Reports\
**Created:** [July 29, 2026, 12:39pm UTC](https://openfhe.discourse.group/t/malformed-binfhecontext-archive-can-trigger-a-heap-buffer-overflow-in-ringgswcryptoparams-precompute/2352 "2026-07-29T12:39:22Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![ypolyakov](https://yyz1.discourse-cdn.com/flex031/user_avatar/openfhe.discourse.group/ypolyakov/32/47_2.png) [@ypolyakov](https://openfhe.discourse.group/u/ypolyakov)\
**Post date:** [August 3, 2026, 6:43pm UTC](https://openfhe.discourse.group/t/malformed-binfhecontext-archive-can-trigger-a-heap-buffer-overflow-in-ringgswcryptoparams-precompute/2352/2 "2026-08-03T18:43:07Z")

</div>

Just like in [[Question / parser robustness report] BFVrns ciphertext deserialization can reach impractical allocation requests from malformed ciphertext metadata - #2 by ypolyakov](https://openfhe.discourse.group/t/question-parser-robustness-report-bfvrns-ciphertext-deserialization-can-reach-impractical-allocation-requests-from-malformed-ciphertext-metadata/2344/2), our focus is on the honest-but-curious model. The issues dealing with malicious adversaries are not our primary focus because FHE is typically instantiated under the honest-but-curios model.

---

_[View the full topic](https://openfhe.discourse.group/t/malformed-binfhecontext-archive-can-trigger-a-heap-buffer-overflow-in-ringgswcryptoparams-precompute/2352)._