Six new CVEs: Samsung, Apache Shiro, router, Estatik
Six CVEs, one new: Samsung mTower ·
In this episode
- CVE-2026-129444: DSL-6740C
- CVE-2026-129349: Apache Shiro
- CVE-2026-125795: Estatik
- CVE-2026-129542: Samsung Open Source Starfish
- CVE-2026-129543: Samsung Open Source Starfish
- CVE-2026-129606: Samsung Open Source mTower
The facts
- CVE-2026-129444 is a flaw in DSL-6740C.
- CVE-2026-129349 is a flaw in Apache Shiro.
- CVE-2026-125795 is a flaw in Estatik.
- CVE-2026-129542 is a flaw in Samsung Open Source Starfish.
- CVE-2026-129543 is a flaw in Samsung Open Source Starfish.
- CVE-2026-129606 is a flaw in Samsung Open Source mTower.
- CVE-2026-129444 is classed as hard-coded credentials (CWE-798).
- CVE-2026-129349 is classed as improper authentication (CWE-287).
- CVE-2026-125795 is classed as remote file inclusion (CWE-98).
- CVE-2026-129542 is classed as files exposed to outside parties (CWE-552).
- CVE-2026-129543 is classed as type confusion (CWE-843).
- CVE-2026-129606 is classed as buffer overflow (CWE-120).
Sources
The panel
Jordan Pike AI host
CVE-2026-129606 is a flaw in Samsung Open Source mTower, and it is classed as buffer overflow (CWE-120).
Maya Okafor AI analyst
Buffer overflow is the old classic: code copies data into a space without checking that it fits. A complete fix enforces bounds everywhere that data is copied, not just in one spot, so check for sibling copies nearby. Whether a patch exists isn't in the facts yet, so the first job is finding out whether you ship mTower at all.
Dex Moreno AI analyst
This class matters because memory corruption can sometimes turn into code running on the host, and a foothold like that is only the start. From there the question is what the host trusts. Exposure decides your order: the more reachable the component, the sooner it goes to the front of the queue.
Jordan Pike AI host
CVE-2026-129543 is a flaw in Samsung Open Source Starfish, and it is classed as type confusion (CWE-843).
Maya Okafor AI analyst
Type confusion means the code treats data as one kind of thing when it is another. A real fix validates types wherever that data is handled, so look for neighbouring code with the same assumption. The facts don't say whether a patch is out, so apply one as soon as one ships.
Dex Moreno AI analyst
Bugs in this family are often attractive to attackers because they can end in memory corruption. That's the general pattern, not something the facts say about this case. The practical step is to find out where Starfish sits in your estate and whether anything untrusted can reach it.
Jordan Pike AI host
CVE-2026-129542 is a flaw in Samsung Open Source Starfish, and it is classed as files exposed to outside parties (CWE-552).
Maya Okafor AI analyst
This class is about files that outsiders can reach and shouldn't. A full fix controls access to everything sensitive, not one file. The facts don't say what is exposed, so treat that as unknown and check what your Starfish deployments can serve up.
Dex Moreno AI analyst
Exposed files are a quiet kind of bug, because a leaked configuration or secret can open doors elsewhere. If you find any exposure, rotate whatever might have been readable. Once one secret has leaked, assume it is in use somewhere.
Jordan Pike AI host
CVE-2026-129349 is a flaw in Apache Shiro, and it is classed as improper authentication (CWE-287).
Maya Okafor AI analyst
Improper authentication means the check that proves who you are can be fooled or skipped. Shiro is a library, so the first job is inventory: which of your applications embed it. A complete fix covers every route that checks identity, so test the neighbours of whatever gets patched.
Dex Moreno AI analyst
I'd rank by exposure: internet-facing apps that use Shiro go first, internal ones second. Login components often sit in front of everything else, so a weakness there can matter well beyond the app itself. Maya will tell you to patch them all, and she's right, but the order still matters.
Jordan Pike AI host
CVE-2026-129444 is a flaw in DSL-6740C, and it is classed as hard-coded credentials (CWE-798).
Maya Okafor AI analyst
Hard-coded credentials are a secret baked into the product, and the owner can't change it. A real fix removes the built-in credential rather than swapping in a new one. Whether the vendor has done that isn't in the facts, so check its advisory before you trust the device.
Dex Moreno AI analyst
A password baked into the firmware is a spare key under the doormat, except the doormat ships to every customer. Truly, economies of scale.
Jordan Pike AI host
Free shipping and no returns.
Jordan Pike AI host
CVE-2026-125795 is a flaw in Estatik, and it is classed as remote file inclusion (CWE-98).
Maya Okafor AI analyst
Remote file inclusion means an application can be pushed into loading a file it shouldn't. A complete fix restricts what can be loaded to an approved set, not a filter on bad names. The facts say little more, so find out if you run Estatik and watch for the vendor's fix.
Dex Moreno AI analyst
This class can end with an attacker's code running on a web server, and that is why web-facing instances go first. Beyond that, nothing in the facts says how this one is reached, so don't guess. Know where it runs and be ready to move.
Jordan Pike AI host
Only the mTower entry is new since our last run; the other five are repeats. Monday's job is the same for all six: inventory where each component runs, put the exposed ones first, and apply vendor fixes as they land.