Authenticated metadata tampering via missing ownership check
Published May 12, 2026 · Updated May 12, 2026
Broken access control in Flowsint before 1.2.3 allows remote authenticated users to alter another user's investigation metadata. The PUT /api/investigations/{investigation_id} handler queries only by investigation ID and writes name, description, and status without binding the record to current_user. A valid account and prior knowledge of the victim's investigation ID are required, and the demonstrated consequence is falsification of stored investigation metadata.
Summary
What happened
Broken access control in Flowsint before 1.2.3 allows remote authenticated users to alter another user's investigation metadata. The PUT /api/investigations/{investigation_id} handler queries only by investigation ID and writes name, description, and status without binding the record to current_user. A valid account and prior knowledge of the victim's investigation ID are required, and the demonstrated consequence is falsification of stored investigation metadata.
The record
- CVE
- CVE-2026-42158
- Published
- May 12, 2026
- Updated
- May 12, 2026
- Vendor
- Reconurge
- Product
- Flowsint
- Classifications
- CWE-284, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 12, 2026CVE publishedPublication date reported by the CVE source.
- May 12, 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=< 1.2.3
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.
Public exploit references
- GHSA-5h6v-5hv3-3jjw proof-of-concept scriptproof 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