Summary
100% of all REPORTED Findings have been addressed
- 1Partially Solved
- 1Future Release
- 1Acknowledged
- 7Solved
- 10All Findings
- Critical1
- 1Solved
- High1
- 1Solved
- Medium0
- Low2
- 1P. Solved
- 1Solved
- Informational6
- 4Solved
- 1Ack.
- 1F. Release
Introduction#
The Glow team engaged Halborn to conduct a security assessment on their Glow Vault Solana program beginning on September 29 2025, and ending on October 16, 2025. The security assessment was scoped to the Solana Programs provided in glow-v1 GitHub repository. Commit hashes and further details can be found in the Scope section of this report.
The Glow Vault program allows users to deposit funds that are then operated by designated parties to earn returns. Users deposit funds via direct deposits or margin account transfers into the vault, and are minted a vault token representing shares of the vault. The program charges management and performance fees at the time of withdrawal.
Assessment Summary#
Halborn was provided 2.5 weeks for the engagement and assigned one full-time security engineer to review the security of the Solana Programs in scope. The engineer is a blockchain and smart contract security expert with advanced smart contract hacking skills, and deep knowledge of multiple blockchain protocols.
The purpose of the assessment is to:
Identify potential security issues within the Solana Programs.
Ensure that smart contract functionality operates as intended.
In summary, Halborn identified some opportunities to reduce the likelihood and impact of risks, and the Glow team implemented improvements to address them. The main ones were the following:
Ensure both management and performance fees accounting is correctly handled.Ensure the performance fees are charged on actual profit at the time of withdrawal.Validate that operators have correct permissions.
The recommendation rated as low-risk to validate potentially dangerous or incompatible Token2022 extensions has been partially addressed, with a comprehensive solution already planned by the Glow team for upcoming releases.
Scope#
Findings Overview#
# | Title | Severity | Score | Status |
|---|---|---|---|---|
HAL-01 | Incorrect fees handling | Critical | 9.4 | Solved11/07/2025 |
HAL-02 | Users may pay performance fees from unrealized profits | High | 7.5 | Solved11/07/2025 |
HAL-03 | Missing Token 2022 extensions validation | Low | 3.0 | Partially Solved10/22/2025 |
HAL-04 | Insuffient operator permissions check | Low | 2.5 | Solved10/22/2025 |
HAL-05 | Incorrect pending withdrawal shares calculation | Informational | 1.3 | Solved10/22/2025 |
HAL-06 | Reliance on Manual or Off-Chain Actions | Informational | 1.3 | Acknowledged11/05/2025 |
HAL-07 | Incorrect redundant position freshness validation | Informational | 0.6 | Solved11/23/2025 |
HAL-08 | Missing instructions to withdraw uncollected fees | Informational | 0.5 | Future Release10/24/2025 |
HAL-09 | Unnecessary Token program resolution | Informational | 0.0 | Solved11/23/2025 |
HAL-10 | Passing unnecessary accounts | Informational | 0.0 | Solved10/22/2025 |
Disclaimer#
Halborn strongly recommends conducting a follow-up assessment of the project either within six months or immediately following any material changes to the codebase, whichever comes first. This approach is crucial for maintaining the project’s integrity and addressing potential vulnerabilities introduced by code modifications.
