Connectivity Intel: Peplink Patches, Verizon Forum Closes

A quiet week on the carrier side, a loud one on the firmware side. Here is what mattered between August 24 and August 31.

Peplink Ships 8.5.5 Alongside Five Security Advisories

The biggest item of the week: Peplink published router firmware 8.5.5 and 8.3.2 GA on August 26, paired with five security advisories covering Balance, MAX, and FusionHub. The advisories include a Web Service components vulnerability tracked as CVE-2026-42945, an SSH CLI command injection issue, an SSH CLI component with multiple vulnerabilities affecting builds up to 8.5.4, a Web Admin flaw that could allow unauthenticated access to internal binaries, and an AirSnitch vulnerability affecting Balance and MAX units with built in Wi-Fi.

One detail worth knowing before you go hunting in InControl: 8.5.5 is not a general upgrade path. Peplink staff clarified in the release thread that 8.5.5 is aimed at units sitting on 8.5.4 that will not be moving to 8.6.0. Several users reported not seeing it offered in InControl at all, which is expected behavior rather than a bug. If your fleet is on the 8.6.0 track, that is where your fixes live.

Also out this week: AP firmware 3.9.8 RC1 on August 30, and continued activity on the 5G dongle firmware 2.0.3 RC1 thread.

Teltonika RutOS 7.24.x Regressions Keep Stacking Up

Teltonika community traffic was dominated by upgrade problems this week, and the pattern is consistent enough to be worth a pause before you push 7.24.x across a fleet. Reported in the last seven days: RUTC50 units failing the upgrade to 7.24.3 outright, an OpenSSL 3.5 regression on RUT241 with missing algorithms in the stable channel, https_proxy breaking on RUT260 after moving from 7.24.1 to 7.24.3, Tailscale breaking on RUTX50 after 7.24.1, a bootloader version that appears to have regressed on 7.24.2, and a webfilter plugin that stopped working on RUT200 post update. One user reported a bricked TRB140 and was asking for fastboot recovery files.

Separately, a cluster of RMS complaints ran through the week, covering remote access login failures, device onboarding, and a TAP400 trial that would not activate. None of this is a reason to avoid the platform, but it is a strong argument for staging upgrades on a test unit first.

Verizon Retired Its Community Forum

Verizon’s community forum is gone. community.verizon.com now redirects to a support landing page flagged with a “community sunset” parameter. The forum went read only in mid July and was retired on August 18, ending an eighteen year run.

For anyone who supports Verizon 5G Home or Business Internet, this is a real loss. A large archive of user written troubleshooting, much of it covering gateway quirks that never made it into official documentation, is no longer reachable. If you had bookmarked threads there, they are not coming back. Worth checking your internal notes for links that now dead end.

Firmware and Security Watch

Beyond Peplink and Teltonika, the week was mostly quiet on the vendor front.

Cradlepoint has NetCloud OS 7.26.80 and a 7.26.80 FR1 build documented for August 2026, though the release note pages render dynamically and we could not confirm whether FR1 landed inside this specific week. If you run NetCloud, check your release channel directly.

Digi forums were unusually quiet, with only two threads in the window and both on the XBee 3 Cellular side. No router firmware or advisories. On the Semtech and Sierra Wireless forum, AirLink activity centered on an RV50X radio connectivity thread and recurring XR80 and XR90 documentation gaps, including band reporting inconsistencies. No ALEOS release or advisory was posted in the window.

Inseego published no news between August 24 and 31. The most recent items on its newsroom are dated August 5. Verizon’s MiFi X PRO 5G UW software update page still lists February 2024 as the newest build, so no change there either.

On the RouterCVE report card, our tracked brands are holding up well. Peplink, Cradlepoint, Digi, and Inseego all sit at A+ with zero CVEs in the last 30 days. Teltonika is at A with 2, and Semtech at A minus with 2. Katalyst remains NR, too new to rate, with a single CVE on record. The contrast with the consumer and legacy enterprise side is stark: Cisco logged 43 CVEs in 30 days, Ubiquiti 22, GL.iNet 21, TRENDnet 18, TP-Link 12, and Palo Alto Networks 12. If you are fielding migration questions from customers on those platforms, those numbers make the case better than we can.

Spectrum and Industry

The FCC had a light week for anything router adjacent. Two actions are confirmed inside the window. On August 25 the Commission released a public notice seeking comment on spectrum for space launch activities, asking whether the 215 MHz currently allocated on a secondary basis is sufficient, with comments due September 14. On August 27 it released the FY 2026 regulatory fees order, which declined to create a new fee category for equipment certification labs.

The more consequential regulatory thread for our industry moved just before this window rather than during it. The FCC’s Covered List entry for routers, added in March, is scoped by place of production and defines “routers” using NIST IR 8425A, which describes consumer grade devices intended for residential use and customer installation. On its face that does not reach industrial and enterprise cellular gateways, and the Commission has not published a clarifying FAQ on where that boundary sits. Conditional approvals continued to be issued through mid August. We are watching this closely and will flag it the moment the scope question gets answered.

Elsewhere: AT&T confirmed on a support page updated August 27 that Internet Air is going up 5 dollars per month starting September 28 for plans activated before October 2025. Affected customers should see a rate plan change notice in their billing center. Optimum announced it will begin using T-Mobile’s 5G standalone core for mobile services. And an analysis piece on fixed wireless capacity in dense urban markets is worth a read if you sell FWA into metro areas, since availability ceilings are becoming a live constraint.

Starlink had no incidents on its status page for the entire window and no new pricing moves. The Roam restructuring and residential increases we covered last week are still the operative changes. On the infrastructure side, SpaceX flew what it says is the last planned Starlink mission from Cape Canaveral until Starship begins flying from Florida, shifting cadence to Vandenberg.

One note on sourcing: Reddit remains inaccessible to our research tooling, so social chatter was not captured this week. AT&T’s own community forum also returned only stale cached content and could not be surveyed.

5Gstore Take

Two practical takeaways this week.

First, patch Peplink, but read the advisory notes before you touch InControl. The 8.5.5 release is narrowly targeted and the absence of an upgrade prompt is not a failure. Knowing which track your units are on, 8.5.x versus 8.6.0, determines what you actually need to do. If you are not sure, that is a five minute conversation.

Second, stage your Teltonika upgrades. The volume of 7.24.x regression reports in a single week is high enough that pushing to production without a canary unit is asking for a truck roll. An OpenSSL regression and a broken bootloader version are not the kind of thing you discover conveniently.

The broader pattern remains the one we keep pointing at. The gap between purpose built cellular and industrial gear and consumer or aging enterprise hardware is not closing, it is widening, and the CVE counts make that legible in a way that spec sheets do not.

Questions about which firmware track your fleet is on, or whether a migration makes sense? Get in touch and we will work through it with you.