# Magellan Vulnerbility

**URL:** <https://discuss.zetetic.net/t/magellan-vulnerbility/3290>\
**Category:** SQLCipher\
**Created:** [December 15, 2018, 2:21am UTC](https://discuss.zetetic.net/t/magellan-vulnerbility/3290 "2018-12-15T02:21:09Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![brodybits](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.zetetic.net/brodybits/32/515_2.png) [@brodybits](https://discuss.zetetic.net/u/brodybits)\
**Post date:** [December 16, 2018, 5:02pm UTC](https://discuss.zetetic.net/t/magellan-vulnerbility/3290/5 "2018-12-16T17:02:34Z")

</div>

FYI it should be possible for any developer to update SQLCipher to SQLite 3.26.0 as described in [https://discuss.zetetic.net/t/sqlcipher-sqlite-update/2470](https://discuss.zetetic.net/t/sqlcipher-sqlite-update/2470).

I hope to see this update on SQLCipher ASAP. While a patch on FTS3 should be good enough I would really favor a clean SQLite 3.26.0 update.

Someone also raised a GitHub issue in [https://github.com/sqlcipher/sqlcipher/issues/297](https://github.com/sqlcipher/sqlcipher/issues/297). I _think_ this is the right place to discuss the wanted update but am not 100% sure.

---

_[View the full topic](https://discuss.zetetic.net/t/magellan-vulnerbility/3290)._