What happened
Summary of Across Protocol V5 audit reveals no critical or high-severity issues but leaves some items unresolved.
Why it matters
The audit indicates an absence of critical and high-severity issues in the summary; however, the presence of unresolved items necessitates reviewing the full report before drawing final conclusions.
OpenZeppelin News and Research published a summary of the audit for the Across Protocol V5ridging system. The assessment took place from July 6o July 22, 2026, and covered Solidity code.
A total of 19 issues were identified: 12 have been resolved, and one has been partially resolved. No critical or high-severity issues were recorded; two medium-severity issues were fully resolved. Of seven low-severity findings, three have been fixed.
Additionally, auditors noted eight informational remarks, seven of which have been addressed. In a separate category of client-reported issues, two items are listed: one is partially resolved, and neither is marked as fully resolved.
This publication serves as a formal summary of the audit status but does not disclose the specific content of the findings nor confirm independent verification by another source. A full review of the audit report and further status updates are required to assess remaining risks.
Confirmed facts
- OpenZeppelin News and Research published a material titled "Across Protocol V5 Bridging System Audit".
- The audit was conducted from July 6o July 22, 2026.
- The audit pertains to the DeFi sector and Solidity code.
- The summary lists a total of 19 issues: 12 resolved, one partially resolved.
- No critical issues are listed; no high-severity issues are listed.
- Two medium-severity issues have been resolved.
- Of seven low-severity issues, three have been resolved.
- Eight additional remarks were recorded, seven of which have been resolved.
- Two issues reported by the client are noted; neither is marked as fully resolved, and one is partially resolved.
- The material was published on August 17, 2026.
Context
The only available source is the OpenZeppelin News and Research summary with a metadata_only limitation; the full audit text and independent confirmations are absent from the package.
What remains unknown
- What is the content of the 19 identified issues?
- Which specific items remain unresolved or partially resolved?
- What do the two client-reported issues entail, and why is one of them only partially closed?
- Has the full audit text containing recommendations and confirmation of fixes been published?
Editorial context
Confidence: high
Likely implication: The published summary reduces uncertainty regarding the formal audit but does not replace verification of the full report and fix statuses. The next observable signal would be the publication of finding details or an update on remaining client and low-level items. Significant uncertainty remains due to the absence of the full audit text and independent confirmation.