If I turn off a feature in a blogging platform, I expect the software to remember that little detail before it starts processing requests. Older versions of Apache Roller do things in the opposite order. That would be an irritating design decision on a good day. This week, Apache confirmed that attackers are exploiting it.
Roller gets the first spot in this week’s roundup because anyone still running an affected blog has a reason to act today. Debian also delivered a Sunday WebKitGTK update worth installing even if you spend most of your time in Firefox. And for those of us who have ever looked at a Linux package version and wondered whether it was actually patched, nginx provides a particularly good example.
Apache Roller admins should check the version even if XML-RPC is off
The uncomfortable part of the Apache Roller advisory is how easy it would be for a careful administrator to get this wrong. You could open the dashboard, confirm that XML-RPC was disabled, and reasonably move on to the next thing on your Sunday to-do list. Meanwhile, the vulnerable endpoint could still process a malicious request before Roller checked either the setting or the visitor’s credentials. An attacker could run code without signing in.
Upgrade to Roller 6.1.6 or later. The November 17 disclosure, CVE-2026-129448, covers versions 4.0.0 through 6.1.4. The earlier identifier, CVE-2026-82384, covered 6.1.5. If you can’t upgrade immediately, Apache says to set enabledForExtensions to false in WEB-INF/web.xml, or remove the /roller-services/xmlrpc servlet mapping, then restart Roller. CISA added the expanded entry to its exploited-vulnerability catalog on November 20.
Debian has a browser fix for people who never open that browser
Ask a Linux user which browser they run and you’ll probably get a quick answer. Ask which web engine their desktop applications use to display a page inside a window and you may get a much longer pause. That second question is the reason I’d install Debian’s November 22 WebKitGTK update. Your choice of default browser tells you very little about what another application loads.
Debian’s advisory covers 24 vulnerabilities. Six, including CVE-2026-112623 and CVE-2026-112626, could allow code execution when an application renders malicious web content. Another, CVE-2026-113897, could allow a remote attacker to escape the web content sandbox. Neither Debian nor the WebKitGTK project reported an attack chaining those flaws. On Debian 13, install the webkit2gtk security update at 2.54.3-1~deb13u1 or later and restart applications that use it.
There’s a wrinkle for anyone keeping an older machine on Debian 12. Debian marks its webkit2gtk package as having reached the end of security support, and its tracker still lists the sandbox flaw as unfixed there. Before using a Bookworm application to open untrusted web content, check whether it relies on that system library or ships a maintained runtime of its own.
Why nginx 1.26 can already have the fix
The nginx security advisories point to 1.30.7 and 1.31.9 as the fixed upstream releases for several flaws, including HTTP/2 memory corruption tracked as CVE-2026-123007. Yet Debian 13 users can install the security update, check the version, and still see 1.26.3. Before you spend Sunday afternoon replacing a perfectly good package, read the rest of its version number.
Debian backported the fixes to 1.26.3-3+deb13u11. Ubuntu did the same for its supported releases, including 1.24.0-2ubuntu7.20 on 24.04 LTS and 1.18.0-6ubuntu14.23 on 22.04 LTS. For administrators running an internet-facing reverse proxy, the job is to install the package for the distribution, restart nginx, and check any separately deployed proxy containers. A host update won’t replace the nginx binary inside an existing image. Debian and Ubuntu list their exact revisions.
How exposed is the server? That depends in part on whether it uses HTTP/2, HTTP/3, the resolver, or the mail proxy. Red Hat reports public proof-of-concept material, and Ubuntu says code execution through the HTTP/2 flow-control flaw requires address space layout randomization to be disabled or bypassed. The reviewed advisories establish a reason to patch promptly. Confirmed attacks would be a separate development.
Ruby runs into trouble changing the case of a string
Converting text to uppercase sounds like the least adventurous thing a programmer could do with it. In a vulnerable Ruby application, that operation on attacker-supplied text in certain encodings, including Windows-1252, can write one byte past an allocated buffer. One byte sounds almost reassuring until you read the Ruby team’s advisory. Researchers demonstrated that this flaw, CVE-2026-132825, can lead to remote code execution in some circumstances.
It’s one of seven issues Ruby disclosed on November 18. Several others involve regular expressions, particularly in applications that let users supply patterns for Ruby to compile. The fixed upstream releases are 3.3.14, 3.4.13, and 4.0.10. If you maintain a Ruby service, check which interpreter the running application uses. Updating Ubuntu’s Ruby package helps a service using Ubuntu’s Ruby. A container or application-managed installation needs its own update.
GPGME is a good reason to ask what an app ships
You don’t have to recognize the name GPGME to use software that depends on it. Mail clients and other applications use the library to work with OpenPGP. On November 20, the GnuPG project warned that processing a key with a specially crafted user ID could cause an application to free the same memory twice and expose data. The developers say they cannot rule out remote code execution for CVE-2026-129975. That’s a more limited claim than the working demonstrations Ruby reported.
Upstream recommends GPGME 2.3.1. Arch has 2.3.1-1 in Core, while Debian backported the fix to 1.18.0-3+deb12u1 for Debian 12 and 1.24.2-3+deb13u1 for Debian 13. Update the shared library and restart applications that load it. If an application has GPGME compiled into its executable, the fix has to come in a rebuilt copy of that application. That’s the package I’d want to hear about from my mail client’s developer.
Support independent tech journalism
NERDS.xyz is independently owned and operated. If you enjoy my coverage of Linux, AI, hardware, cybersecurity, and tech culture, consider supporting the site on Ko-fi.
Support NERDS.xyz

