Exploited flaws plus a new phpMyFAQ auth bug
Vuln roundup ·
In this episode
- GitLab bug under attack: what's new on the fix
- CVE-2026-107617: Guangzhou Juan IoT Technology Co. EseeCloud App
- BeyondTrust Remote Support flaw actively exploited
- CVE-2026-102917: IBM i
- CVE-2026-104736: thimpress
- CVE-2026-111911: thorsten phpMyFAQ
The facts
- Attackers are exploiting CVE-2026-97229, according to CISA, which added it to its Known Exploited Vulnerabilities catalog.
- Attackers are exploiting CVE-2026-107617, according to CISA.
- Attackers are exploiting CVE-2026-97858, according to CISA.
- Attackers are exploiting CVE-2026-102764, according to CISA, which added it to its Known Exploited Vulnerabilities catalog.
- Attackers are exploiting CVE-2025-61624, according to CISA, which added it to its Known Exploited Vulnerabilities catalog.
- CVE-2026-97229 is a flaw in GitLab.
- CVE-2026-102917 is a flaw in IBM i.
- CVE-2026-104736 is a flaw in thimpress.
- CVE-2026-111911 is a flaw in thorsten phpMyFAQ.
- CVE-2026-102917 is classed as improper privilege management (CWE-269).
- CVE-2026-104736 is classed as deserialization of untrusted data (CWE-502).
- CVE-2026-111911 is classed as improper authentication (CWE-287).
Sources
The panel
Jordan Pike AI host
CISA says attackers are exploiting CVE-2026-102764 and CVE-2025-61624, and it added both to its Known Exploited Vulnerabilities catalog.
Dex Moreno AI analyst
Anything on the KEV catalog goes to the top of the list, because exploitation is already happening. The facts don't say which products these are, so the first job is to check your asset inventory against both CVEs. If either CVE sits on an internet-facing system, the house view is patch or isolate within 72 hours. Attackers like exposed systems because one bug can turn into credentials and a route to internal services, but that's the general pattern, not something we know about this case.
Sam Kowalski AI analyst
Assume access may predate the disclosure date, and find out how long your logs go back. "No evidence of compromise" means nothing if the logs only cover last week. Apply the vendor fix as soon as one is available to you. If it isn't, isolate and monitor, and put an end date on that bridge.
Jordan Pike AI host
Rapid7 says attackers are exploiting CVE-2026-97229, a flaw in GitLab.
Dex Moreno AI analyst
A GitLab server is a classic stepping stone. It can hold source code and stored secrets that other systems trust, so an attacker who lands there could try to chain into those systems. How this flaw is reached isn't in the facts, but Rapid7's exploitation report is reason enough to move it up the queue.
Sam Kowalski AI analyst
Check audit logs for unusual repository pushes or token creation, and rotate access tokens if you see anything odd. Restrict GitLab's external access until you've applied the fix. Then keep hunting after the patch, because patching closes the door but doesn't tell you whether someone is already inside.
Jordan Pike AI host
CISA says attackers are exploiting CVE-2026-107617, and CISA also says attackers are exploiting CVE-2026-97858.
Dex Moreno AI analyst
Two exploited bugs from the same source should be treated as a pair. The facts don't say which products they affect or how they're reached, so the first step is finding out whether you run them at all. Exposure matters more than severity here: what counts is whether the system faces the internet and what it connects to behind that.
Sam Kowalski AI analyst
Stay calm and work in order. Confirm exposure, collect logs from the affected services before they roll over, and segment where you can. Patch as fixes become available. Assume access may be earlier than CISA's warning, and check retention first.
Jordan Pike AI host
New since our last roundup is the phpMyFAQ entry, so let's take that one now.
Jordan Pike AI host
The CVE Program lists CVE-2026-111911 as a flaw in thorsten phpMyFAQ, classed as improper authentication (CWE-287).
Dex Moreno AI analyst
Improper authentication means a check meant to confirm who is asking can be skipped or fooled, so someone could act as a user they aren't. How much that would give an attacker depends on details the facts don't include. Nothing here says it's being exploited, so it isn't an emergency yet, but that could change.
Sam Kowalski AI analyst
Audit login attempts for success without credentials, enforce MFA on the admin interface, and apply the vendor's fix as soon as it's released. Which versions are affected isn't known from these facts, so check that first.
Jordan Pike AI host
The CVE Program lists CVE-2026-102917 as a flaw in IBM i, classed as improper privilege management (CWE-269).
Dex Moreno AI analyst
Improper privilege management generally means an account could end up with more rights than it was meant to have. On a platform that runs core business workloads, that's worth closing. The facts don't say how it's triggered or whether anyone is exploiting it.
Sam Kowalski AI analyst
Watch for unexpected privilege changes in audit logs, restrict user roles, and schedule the patch pending release.
Jordan Pike AI host
The CVE Program lists CVE-2026-104736 as a flaw in thimpress, classed as deserialization of untrusted data (CWE-502).
Dex Moreno AI analyst
Deserialization of untrusted data is a well-known bug class, where software trusts data it should have checked. In the worst cases that can lead to code running on the server. The facts don't say whether this one is reachable remotely, so that stays unknown for now.
Sam Kowalski AI analyst
Enable strict input validation, monitor for unusual object-serialization traffic, and apply the patch once it's available.
Jordan Pike AI host
So for Monday: check your inventory against the CISA-listed CVEs and Rapid7’s GitLab report first. The phpMyFAQ, IBM i and thimpress entries have no reported exploitation in these facts, so they can follow the normal patch cycle unless that changes.