Authenticated integration enumeration via missing admin check
Published Jul 7, 2026 · Updated Jul 7, 2026
Improper authorization in Actual before 26.6.0 allows remote authenticated users to enumerate bank-sync integrations via API requests. GET /secret/:name validates a session but omits the OpenID admin check, exposing secret existence through distinct 204 and 404 responses. Exploitation requires a BASIC user in an OpenID multi-user deployment with configured integrations; values cannot be read or changed.
Summary
What happened
Improper authorization in Actual before 26.6.0 allows remote authenticated users to enumerate bank-sync integrations via API requests. GET /secret/:name validates a session but omits the OpenID admin check, exposing secret existence through distinct 204 and 404 responses. Exploitation requires a BASIC user in an OpenID multi-user deployment with configured integrations; values cannot be read or changed.
The record
- CVE
- CVE-2026-46700
- Published
- Jul 7, 2026
- Updated
- Jul 7, 2026
- Vendor
- Actual Budget
- Product
- Actual
- Classifications
- CWE-285
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 7, 2026CVE publishedPublication date reported by the CVE source.
- Jul 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 26.6.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream HTTP proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo