Reported exploitation of Bricksforge file-upload flaw
Bricksforge CVE-2026-85097 ·
In this episode
The facts
- Attackers are reported to be exploiting CVE-2026-85097.
- Attackers are reported to be exploiting Bricksforge.
- CVE-2026-85097 is a flaw in Bricksforge.
- CVE-2026-85097 is classed as unrestricted file upload (CWE-434).
- According to its CVSS rating, CVE-2026-85097 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-85097 is rated 9.8 out of 10 on the CVSS severity scale.
- FIRST's EPSS model puts the chance that CVE-2026-85097 is exploited in the next 30 days at 0.3 percent.
Sources
The panel
Jordan Pike AI host
The Hacker News reports attackers are exploiting CVE-2026-85097, which has not been confirmed, and SC Media reports attackers are exploiting Bricksforge, which has not been confirmed.
Jordan Pike AI host
CVE-2026-85097 is a flaw in Bricksforge, classed as unrestricted file upload (CWE-434). It is rated 9.8 on the CVSS severity scale and can be exploited remotely over the network without credentials or user interaction, fully compromising confidentiality, integrity and availability.
Jordan Pike AI host
FIRST’s EPSS model puts the chance that CVE-2026-85097 is exploited in the next 30 days at 0.3 percent.
Maya Okafor AI analyst
Unrestricted file upload lets an attacker place any file on the server, a well-known route to remote code execution. The weakness often survives because developers rely on ad-hoc checks instead of systematic validation. A complete mitigation requires rejecting any upload that could be interpreted as code, storing files in a location that the web server cannot execute, and ensuring only intended file types are accepted. Until a full patch ships, a temporary blocklist can reduce risk but does not eliminate the underlying problem.
Maya Okafor AI analyst
A blocklist. Bold. Nothing says 'root cause' like a list of words you'd rather not see.
Jordan Pike AI host
Somebody check that list for the word 'patch'.
Dex Moreno AI analyst
With an unrestricted upload, an attacker can drop a web shell and obtain full control of the host, matching the confidentiality, integrity and availability impact described by the CVSS. From that foothold they can enumerate internal services, harvest credentials and move laterally across the network, potentially reaching databases or other critical assets. Even though FIRST predicts a low short-term exploitation chance, the high severity means any active exploit would be extremely damaging.
Dex Moreno AI analyst
Looks like the attackers think 'unrestricted' is a permission setting.
Jordan Pike AI host
Permissions, but make it optimistic.
Maya Okafor AI analyst
I’d argue that patching the upload logic is the only way to close the attack surface; simply isolating the server leaves the vulnerable code in place and invites future abuse, especially as attackers can discover alternate entry points.
Dex Moreno AI analyst
Isolation buys you precious time to test and deploy a fix, and you can block the upload endpoints at the perimeter while you verify the patch works. It’s a practical bridge until a full remediation is in place, and it reduces the window of exposure.
Sam Kowalski AI analyst
To determine whether a web shell is already present, pull the web server access logs and look for POST requests that uploaded executable files, then hash the uploaded content and compare against known payload signatures. Also review system processes for unexpected interpreter instances. Preserve all relevant logs for a sufficient retention period to support any later investigation. Assume access may predate the reports, so find out how far back your logs actually go before anyone says the word clean.
Rina Takahashi AI analyst
There’s no confirmed attribution; the reports are unverified and no group has claimed the Bricksforge abuse. Historically, ransomware operators and hack-tivist collectives have leveraged unrestricted upload bugs, so keep those feeds on your radar. Treat every claim as someone's claim, and ask who says so and how confident they are. Action: add “Bricksforge file-upload” to your threat-intel watchlist.
Jordan Pike AI host
If your organization runs Bricksforge, treat this 9.8-rated flaw as an emergency – patch or isolate the affected systems within the next 72 hours. That’s the Monday move.