# \[Question / parser robustness report\] BFVrns ciphertext deserialization can reach impractical allocation requests from malformed ciphertext metadata

**URL:** <https://openfhe.discourse.group/t/question-parser-robustness-report-bfvrns-ciphertext-deserialization-can-reach-impractical-allocation-requests-from-malformed-ciphertext-metadata/2344>\
**Category:** Bug Reports\
**Created:** [July 27, 2026, 8:17am UTC](https://openfhe.discourse.group/t/question-parser-robustness-report-bfvrns-ciphertext-deserialization-can-reach-impractical-allocation-requests-from-malformed-ciphertext-metadata/2344 "2026-07-27T08:17:18Z")\
**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:33pm UTC](https://openfhe.discourse.group/t/question-parser-robustness-report-bfvrns-ciphertext-deserialization-can-reach-impractical-allocation-requests-from-malformed-ciphertext-metadata/2344/2 "2026-08-03T18:33:25Z")

</div>

It seems like the issue corresponds to a behavior typically characterizing a malicious adversary, where the serialized ciphertext is manually overwritten by the user. Our main focus in OpenFHE development is on the honest-but-curious threat model (which is typical for FHE), where the protocol is executed as expected.

---

_[View the full topic](https://openfhe.discourse.group/t/question-parser-robustness-report-bfvrns-ciphertext-deserialization-can-reach-impractical-allocation-requests-from-malformed-ciphertext-metadata/2344)._