In 30 seconds

Apache has expanded its security warning for Roller, its Java-based blogging platform, and now says the flaw is being exploited in real attacks. The bug, tracked as CVE-2026-129448, carries a severity score of 9.8 out of 10 and hits versions 4.0.0 through 6.1.4. The fix landed in 6.1.6, and 6.1.7 is the current security release.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source listDarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
According to Apache, attackers are already abusing the flaw to run arbitrary commands on unpatched servers, with no password or account needed. Turning off XML-RPC in the admin interface does not protect older releases, because the dangerous code runs before that setting is ever checked. Who the attackers are and how many servers were hit is not known.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source listDailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list
What happened
The update came through Apache's advisory on the oss-security mailing list, covered the same day by BleepingComputer. The advisory states that CVE-2026-129448 is actively exploited and that it widens the affected-version coverage of an earlier bug, CVE-2026-82384, which had listed only version 6.1.5.openwall.comopenwall.com · rssOpen original sourceSee in source listDailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source listbleepingcomputer.combleepingcomputer.com · rssOpen original sourceSee in source list
Under the hood, older Roller releases deserialize incoming XML-RPC data, meaning they turn raw requests into live Java objects, before checking authentication or the admin UI's XML-RPC switch. Apache rates the impact as unauthenticated remote code execution: a crafted request can run commands on the server without a valid login. The patch shipped in 6.1.6, and 6.1.7 now stands as the current security release with additional fixes.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source listDarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
The exploitation claim is Apache's own. The foundation says attacks are under way, while the identities of the attackers and the number of compromised servers remain unknown.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
Why it matters
An unauthenticated flaw lowers the cost of attack dramatically. There is no password to steal and no account to phish: per the advisory, anyone who can reach the XML-RPC endpoint of an exposed Roller install can take over the underlying server. Internet-facing blogs on old versions are the obvious surface.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source listDailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list
The UI toggle detail makes this worse than it looks. Many admins will assume that switching XML-RPC off in the interface counts as a mitigation, and on these older versions it simply does not, since the risky deserialization happens first. That false sense of safety is exactly why an explicit exploitation warning matters.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list
What to do
Apache urges administrators to upgrade immediately. The safest target is 6.1.7, the current security release, which also fixes other issues. Anything below 6.1.6 remains vulnerable.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source listDarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
If an upgrade cannot happen right away, Apache publishes a configuration workaround for admins who need a stopgap. Apply it and restart the service as instructed.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list
Confirmed and still uncertain
What is established: the flaw is unsafe deserialization in the XML-RPC endpoint, CVE-2026-129448 affects Roller 4.0.0 through 6.1.4 with 6.1.5 covered separately by CVE-2026-82384, the CVSS 3.1 score is 9.8, and fixed code ships in 6.1.6 and later.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list
What is not: no campaign details, no victim counts and no attribution have been made public. DarkWebInformer notes that the attackers' identities and the number of compromised servers remain unknown.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source listDailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list
Whether the exploitation is opportunistic scanning of the internet or deliberate targeting is impossible to say from the current evidence.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
What people are saying
Security channels on X amplified the warning quickly. DarkWebInformer framed it as hackers exploiting a critical flaw to take control of servers without authentication, while DailyDarkWeb stressed the practical trap: turning off XML-RPC in the UI is not enough.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source listDailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list
DailyDarkWeb also offered a useful calibration for anyone confused by fresh headlines: this is an expanded advisory and an exploitation warning, not a new patch. The fix itself shipped earlier, in 6.1.6. BleepingComputer's account linked straight to its story.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source listBleepinComputerx.com · BleepinComputer · xOpen original sourceSee in source list
Evolution
The timeline has two stages. First came the patch: version 6.1.6 fixed the deserialization flaw, and a separate advisory under CVE-2026-82384 covered version 6.1.5. Then came the escalation: Apache extended the affected range down to 4.0.0 under the new CVE-2026-129448, added the warning that attacks are under way, and issued 6.1.7 as the current security update.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list
Within this evidence batch the story moved in one day: BleepingComputer's report appeared first, followed hours later by the oss-security advisory record and the X posts summarizing it.bleepingcomputer.combleepingcomputer.com · rssOpen original sourceSee in source listopenwall.comopenwall.com · rssOpen original sourceSee in source listBleepinComputerx.com · BleepinComputer · xOpen original sourceSee in source list
Reach
3 independent groups, 3 updates, and 6 engagements.
Technical detail
The root cause is unsafe deserialization in Roller's XML-RPC endpoint. In plain terms, the server converts incoming XML-RPC request data into live Java objects, and it does so before authenticating the caller or consulting the UI setting meant to disable XML-RPC. A malicious request can trigger code execution inside that pre-authentication window. CVSS 3.1 score: 9.8.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source listDarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source list
The CVE bookkeeping trips people up, so it is worth spelling out: CVE-2026-129448 covers versions 4.0.0 to 6.1.4, while CVE-2026-82384 covers 6.1.5. One post described the combined span as 4.0.0 through 6.1.5 with 6.1.5 tracked separately, which matches the advisory's split rather than contradicting it.DarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source listDailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source list
Sources and evidence
The primary records in this batch are Apache's advisory on the oss-security mailing list and BleepingComputer's article. Both arrived as headline records without full body text, so their contribution here is confirmation of publication and timing rather than quotable detail.openwall.comopenwall.com · rssOpen original sourceSee in source listbleepingcomputer.combleepingcomputer.com · rssOpen original sourceSee in source list
The technical specifics therefore come from X posts by DailyDarkWeb and DarkWebInformer that summarize the advisory, plus BleepinComputer linking its own coverage. Treat their wording as summaries of what Apache said, one step removed from the advisory text itself.DailyDarkWebx.com · DailyDarkWeb · xOpen original sourceSee in source listDarkWebInformerx.com · DarkWebInformer · xOpen original sourceSee in source listBleepinComputerx.com · BleepinComputer · xOpen original sourceSee in source list
Sources
- DailyDarkWebx.com · DailyDarkWeb · x
- DarkWebInformerx.com · DarkWebInformer · x
- openwall.comopenwall.com · rss
- bleepingcomputer.combleepingcomputer.com · rss
- BleepinComputerx.com · BleepinComputer · x



