Authenticated S3 bucket write control via filename
Published Aug 11, 2026 · Updated Aug 11, 2026
External filename control in Ivanti Endpoint Manager before 2024 SU7 allows remote authenticated users to write to an S3 recording bucket. The Core accepts an attacker-controlled filename for an S3 write, but Ivanti has not identified the responsible function or validation failure. An authenticated account and an S3 bucket configured for session recording are required; exploitation grants full write control over that bucket.
Summary
What happened
External filename control in Ivanti Endpoint Manager before 2024 SU7 allows remote authenticated users to write to an S3 recording bucket. The Core accepts an attacker-controlled filename for an S3 write, but Ivanti has not identified the responsible function or validation failure. An authenticated account and an S3 bucket configured for session recording are required; exploitation grants full write control over that bucket.
The record
- CVE
- CVE-2026-18127
- Published
- Aug 11, 2026
- Updated
- Aug 11, 2026
- Vendor
- Ivanti
- Product
- Ivanti Endpoint Manager
- Classifications
- CWE-73, CAPEC-122, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 11, 2026CVE publishedPublication date reported by the CVE source.
- Aug 11, 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?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
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
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