Estatik flaw rated 9.8 allows remote file inclusion
Estatik CVE-2026-125795, CVSS 9.8 ·
In this episode
The facts
- CVE-2026-125795 is a flaw in Estatik.
- CVE-2026-125795 is classed as remote file inclusion (CWE-98).
- According to its CVSS rating, CVE-2026-125795 can be exploited remotely over the network, without any credentials and without user interaction. A successful attack would fully compromise the confidentiality, integrity and availability of the affected system.
- CVE-2026-125795 is rated 9.8 out of 10 on the CVSS severity scale.
Sources
The panel
Jordan Pike AI host
CVE-2026-125795 is a flaw in Estatik, classed as remote file inclusion, CWE-98.
Jordan Pike AI host
According to its CVSS rating, CVE-2026-125795 can be exploited remotely over the network, without any credentials and without user interaction. A successful attack would fully compromise the confidentiality, integrity and availability of the affected system. It is rated 9.8 out of 10 on the CVSS severity scale.
Jordan Pike AI host
If you run Estatik anywhere, this one is yours. The facts say nothing yet about a patch, exploitation or who is affected, so we'll stick to what the class means. Dex, how does someone reach this?
Dex Moreno AI analyst
The exploitability facts are the whole story: network reachable, no credentials, no clicking. Nobody has to phish anyone or steal a login first. If the vulnerable component faces the internet, the attacker's first step is just reaching it. File inclusion, as a class, is about getting an application to load content the attacker influences. So the foothold could be code running as the web application, and from there the usual pattern is whatever that app can reach: stored secrets, database credentials, neighbouring systems. That's the general pattern, not something the facts say happened here.
Dex Moreno AI analyst
Remote, no credentials, no user interaction. The attacker's to-do list is basically blank. Truly, a low-maintenance career. The target deserved better.
Jordan Pike AI host
Dex, you sound like you're reading a rental listing.
Maya Okafor AI analyst
Remote file inclusion is an input-handling bug. The application builds the location of a file from something the user controls, then loads it as part of itself. It keeps happening because including files is convenient and checking where they come from is dull. The facts don't say which part of Estatik is affected, so I won't guess.
Maya Okafor AI analyst
Adding it to the tally of bugs that should have died in 2004. The tally is not a short list.
Jordan Pike AI host
At this point the tally needs its own filing cabinet.
Maya Okafor AI analyst
A complete fix means the application never lets user input choose what gets loaded, or only picks from a fixed list it controls. A blocklist of bad strings is a partial fix, and it comes back. Once a patch exists, check that it closes the class and look for sibling include paths nearby. Also inventory every place Estatik is deployed, because you can't patch what you forgot you had.
Dex Moreno AI analyst
Here's where I'd split priorities. Exposure beats score. I'd find which instances face the internet and handle those first, and let the internal ones follow the normal cycle. Everything is a 9.8 on a slide, but only some of it is reachable.
Maya Okafor AI analyst
I'd push back. No credentials, no clicks, full impact: that is not a profile that waits. Whether a fix exists isn't known yet, but when one ships, apply it everywhere, not only where you think the exposure is. Your asset list is probably wrong in at least one place. If you mitigate in the meantime, give the mitigation an end date, because it's a bridge, not a fix.
Sam Kowalski AI analyst
The facts don't say anyone has exploited this, so I won't claim either way. But 'no evidence of compromise' means nothing until you know how long your logs go back. If the web server logs only cover a short window, you can't say much about what happened before it. Assume earlier access is possible, and preserve what you have before it rotates out.
Sam Kowalski AI analyst
Your retention policy is surely fine, I'm sure. Go and check anyway.
Jordan Pike AI host
That reassurance had a very long pause in the middle.
Rina Takahashi AI analyst
On attribution, there is none: no actor is named and no exploitation is reported in the facts. The 9.8 is the CVE Program's severity rating, not a sighting in the wild. If someone later claims exploitation, ask who says so and how confident they are, and treat the claim as a claim until it's confirmed. A high score tells you how bad it could be, not who is using it.
Jordan Pike AI host
Closing actions, one each. Dex?
Dex Moreno AI analyst
Find every internet-facing Estatik instance today and put those at the front of the queue.
Maya Okafor AI analyst
Inventory all deployments now, and apply the fix everywhere the moment one ships.
Sam Kowalski AI analyst
Find out how long your logs go back for anything running Estatik, and preserve them.
Rina Takahashi AI analyst
Watch for any exploitation reports and note who is making them and how confident they are.
Jordan Pike AI host
So Monday: know where Estatik runs, know what's exposed, know how far back your logs go, and patch as soon as a fix is available. Whether one exists isn't known yet.