Cross-operation build-log disclosure via always-true permission branch
Published Jun 29, 2026 · Updated Jun 29, 2026
Incorrect authorization in Mythic before 3.4.0.60 allows remote authenticated users to read payload build logs across operations. The payload_build_step Hasura filter accepts a non-null payloadtype_id as one _or branch, so its operation-membership branch never limits rows. Operator or spectator access to any operation is sufficient to read step output and metadata from every operation on that server.
Summary
What happened
Incorrect authorization in Mythic before 3.4.0.60 allows remote authenticated users to read payload build logs across operations. The payload_build_step Hasura filter accepts a non-null payloadtype_id as one _or branch, so its operation-membership branch never limits rows. Operator or spectator access to any operation is sufficient to read step output and metadata from every operation on that server.
The record
- CVE
- CVE-2026-57951
- Published
- Jun 29, 2026
- Updated
- Jun 29, 2026
- Vendor
- its-a-feature
- Product
- Mythic
- Classifications
- CWE-863, T1213
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 29, 2026CVE publishedPublication date reported by the CVE source.
- Jun 29, 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=0 <3.4.0.60
What conditions does exploitation require?
What is affected?
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.
Public exploit references
No public exploit references are available in this record.
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