Omniscia Tesseract Audit
Earn Vault Security Audit
Audit Report Revisions
| Commit Hash | Date | Audit Report Hash |
|---|---|---|
| 56ad119917 | March 17th 2026 | 2219cec9f0 |
| fdf0694b5c | March 24th 2026 | fc43ce3d72 |
| c39cbc38aa | March 25th 2026 | cba6a5a387 |
Audit Overview
We were tasked with performing an audit of the Tesseract codebase and in particular their Earn Vault module.
The Earn Vault system is composed of three core contracts that all interconnect to support IPOR Fusion PlasmaVault deployments via a dedicated vault deployer with pre-set configurations alongside a ConfigManager instance that permits administrators to establish fuse / substrate configurations that an operator can push to those vaults.
Over the course of the audit, we identified a flaw in the ConfigManager role-based access control system that permits the OPERATOR_ROLE to bypass the authority of the DEFAULT_ADMIN_ROLE as well as a slippage-style flaw in the way vault deployments are processed.
We advise the Tesseract team to closely evaluate all minor-and-above findings identified in the report and promptly remediate them as well as consider all optimizational exhibits identified in the report.
Post-Audit Conclusion
The Tesseract team iterated through all findings within the report and provided us with a revised commit hash to evaluate all exhibits on.
We evaluated all alleviations performed by Tesseract and have identified that a particular exhibit has not been adequately dealt with. We advise the Tesseract team to revisit the following exhibit: CMR-02M
Post-Audit Conclusion (c39cbc38aa)
The Tesseract team provided us with a follow-up commit hash to evaluate the fix implemented for CMR-02M.
We evaluated the fix and confirmed that it has been addressed properly, rendering all outputs of the audit report properly consumed by the Tesseract team.
Audit Synopsis
| Severity | Identified | Alleviated | Partially Alleviated | Acknowledged |
|---|---|---|---|---|
![]() | 0 | 0 | 0 | 0 |
![]() | 7 | 7 | 0 | 0 |
![]() | 2 | 2 | 0 | 0 |
![]() | 1 | 1 | 0 | 0 |
![]() | 0 | 0 | 0 | 0 |
During the audit, we filtered and validated a total of 1 findings utilizing static analysis tools as well as identified a total of 9 findings during the manual review of the codebase. We strongly recommend that any minor severity or higher findings are dealt with promptly prior to the project's launch as they can introduce potential misbehaviours of the system as well as exploits.
Total Alleviations
The list below covers each segment of the audit in depth and links to the respective chapter of the report:




