Security context
What an agent needs to avoid regressing past fixes and find the next vuln in this repo.
ArbitrumFoundation/governance
main @ 9e413da
23
Fixes
0
CVEs
HIGH
Peak severity
58.8%
Coverage
Highlights
Access Control: 15 prior fixes. Scrutinize any change in this area.
src/security-council-mgmt/governors/SecurityCouncilNomineeElectionGovernor.sol: most-fixed (5 issues). Treat as high-risk during review.
21 high-severity fixes in this history; regressions here are high-impact.
Recurring patterns
The bug types that recur here, drawn from past fixes, not open vulnerabilities.
Access Control: Multiple fixes target this governor: state-machine gaps (addContender in Active, includeNominee after vetting deadline, blacklistNominee outside window), caller spoofing (addContender using caller-supplied account), and cohort eligibility bypass. These indicate a systemic weakness in enforcing proposal state and caller identity across nomination lifecycle functions.
Access Control Bypass: Two bypass issues: includeNominee allowed after vetting deadline, and createElection allowed before previous election executed. These are sequencing/state-transition flaws that let unauthorized actions occur outside the intended governance workflow.
Replay Attack: Signature-based voting lacked nonce protection, allowing the same signed vote to be replayed. This is a classic replay vulnerability in a high-impact voting function.