Unauthenticated credential overwrite via serviceKey file write
Published Sep 15, 2026 · Updated Sep 15, 2026
Improper input validation in OpenCost before 1.121.0 allows remote attackers to overwrite its GCP service-account key via POST /serviceKey. The unauthenticated AddServiceKey handler reads the key form value and passes its bytes directly to os.WriteFile at the fixed CONFIG_PATH/key.json path without validating the credential. Reachability to the HTTP service is sufficient; replacing that file can interrupt GCP cost collection or make OpenCost use attacker-selected credentials.
Summary
What happened
Improper input validation in OpenCost before 1.121.0 allows remote attackers to overwrite its GCP service-account key via POST /serviceKey. The unauthenticated AddServiceKey handler reads the key form value and passes its bytes directly to os.WriteFile at the fixed CONFIG_PATH/key.json path without validating the credential. Reachability to the HTTP service is sufficient; replacing that file can interrupt GCP cost collection or make OpenCost use attacker-selected credentials.
The record
- CVE
- CVE-2026-44300
- Published
- Sep 15, 2026
- Updated
- Sep 15, 2026
- Vendor
- OpenCost
- Product
- OpenCost
- Classifications
- CWE-309, CWE-20, T1565.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 15, 2026CVE publishedPublication date reported by the CVE source.
- Sep 15, 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.121.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
- GitHub advisory serviceKey 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