UniFi's $99 Travel Router Sells Out Fast, a Nasty Magento Zero-Day Is Live, and Your Network Isn't Ready for the Next Hurricane

A pocket-sized UniFi router with a folding long-range antenna sold out globally in hours. That's just the start of today's lineup.

The UniFi Travel Router Long-Range Is Real, It's $99, and Good Luck Finding One

Ubiquiti quietly dropped the UniFi Travel Router Long-Range at $99 and the internet responded by immediately emptying the shelves. The headline feature is an adjustable folding antenna designed to pull in signal where a standard travel router would give up — think hotel conference floors, remote job sites, or that vacation rental with the ISP gateway bolted to the ceiling of a back bedroom.

At $99 this thing slots in perfectly between the original Travel Router (great form factor, mediocre range) and dragging a full UniFi stack somewhere you don't own the walls. The folding antenna is a genuine differentiator. It's not cosmetic, it's the reason range-constrained scenarios finally have a first-party answer.

The bad news: "sold out almost immediately following global rollout" is doing a lot of work in that sentence. Check the Ubiquiti store directly and set up a stock alert if you use a browser extension for that. Based on how Ubiquiti handled the original Travel Router launch, expect restocks to trickle in over the next few weeks rather than one big replenishment. Need one for a specific trip or deployment? Don't wait on a restock, plan around it.

Next step: Hit store.ui.com now, add to wishlist, and watch the UniFi subreddit for restock reports.

StyleSmuggler Is Actively Backdooring Magento Stores, Patch or Contain Right Now

This one warrants your full attention. A zero-day tracked as StyleSmuggler is being actively exploited against unpatched Magento and Adobe Commerce installations, delivering unauthenticated remote code execution and dropping persistent backdoors. Unauthenticated RCE means an attacker needs no credentials, they hit your storefront and own it.

If you manage, host, or consult for any e-commerce operation running Magento or Adobe Commerce, treat this as a fire drill happening right now. Shield53's analysis outlines immediate containment steps, and that's your first stop. The short version: isolate the admin panel behind a VPN or IP allowlist immediately, audit recently modified theme and layout XML files (StyleSmuggler hides in CSS/layout injection vectors, hence the name), check for unexpected cron jobs or PHP files in the pub/media directory, and pull your web server access logs for anomalous POST requests to theme endpoints.

There is no vendor patch as of this writing. WAF rules are your best temporary control, Cloudflare, Sucuri, and similar providers are already pushing signatures. On Adobe Commerce Cloud, check Adobe's security advisory channel; managed hosting providers are rolling mitigations at the infrastructure layer.

Don't wait for a patch to act. Containment now beats remediation after a breach.

Next step: Read the Shield53 breakdown, apply WAF rules today, and audit your file system for indicators of compromise.

Your Enterprise Network Has a Climate Problem You Haven't Budgeted For

Computer Weekly's feature on climate resilience and enterprise networking is worth a slow read, not a skim. The core argument: most network architectures are optimized for steady-state performance, not for operating through a Category 3 making landfall, a heat dome that takes out a data center's cooling, or a wildfire that severs your fiber path for two weeks.

Here in Upstate SC we're not immune. We've had ice storms knock out power for days, and the Southeast's hurricane exposure keeps creeping further inland. Just look at what Hurricane Helene did a couple of years ago ranging from here in the Upstate to Western North Carolina. The blind spot the article identifies is that resilience gets treated as a DR checkbox rather than a design principle baked into day-one architecture decisions.

Practically, this means asking harder questions during your next refresh cycle: Are your edge sites on diverse power paths? Do your WAN failover configurations actually get tested under load, or just on paper? Is your out-of-band management accessible when your primary network is down? For UniFi shops specifically, cellular failover via LTE backup is cheap insurance, and if you're not using it on critical sites, you're betting on uptime you don't control.

Good architecture performs well today and adapts when the context changes. Climate disruption is now a context you have to design for.

Next step: Add a climate/resilience review to your next network audit. Start with your single points of failure on power and WAN diversity.

Broadcom Blinks: A New vSphere Standard Tier Is Coming

Broadcom's post-acquisition VMware strategy has been aggressive and alienating in equal measure, pushing everyone toward VMware Cloud Foundation whether they needed it or not. Now, according to CloudNews, Broadcom is preparing a refreshed vSphere Standard tier aimed at organizations that need solid server virtualization without the full VCF platform and its accompanying price tag.

A huge segment of the market, regional businesses, mid-market IT shops, homelab-adjacent small enterprises, got effectively priced out or pushed toward alternatives after the acquisition restructured licensing. Proxmox picked up a lot of those refugees, and Broadcom clearly noticed.

For homelabbers and small shops that stuck with VMware out of familiarity or existing investment: don't rush back yet. Wait for actual pricing and feature details before drawing conclusions. Broadcom has shown a willingness to restructure offerings in ways that look generous on the surface but hide the real costs in support tiers or add-ons. Healthy skepticism is warranted.

Already migrated to Proxmox or Hyper-V? You're probably fine staying put. Competition pushing Broadcom toward a more accessible tier is good for the market regardless of whether you personally benefit.

Next step: Watch for official vSphere Standard pricing announcements before making any platform decisions. Don't let a press release reverse a migration you've already completed.

Stop Running Docker Logic in Your Proxmox LXCs

This XDA piece resonated with me because I've made exactly this mistake. LXC containers in Proxmox are not Docker containers, and the moment you stop treating them like they are, your homelab gets dramatically more useful.

The core insight: Docker containers are designed to be ephemeral, stateless, and disposable. LXCs are lightweight VMs. They have persistent init systems, they run full service stacks, they have their own network interfaces, and they're meant to behave like long-lived Linux machines. Fighting that by trying to replicate Docker's "one process per container" pattern in LXC leaves you with fragile configurations, weird networking headaches, and setups that break on Proxmox updates.

The better mental model is to treat each LXC like a small dedicated server. Install the service, configure it properly with systemd, let it manage its own dependencies. For things that genuinely benefit from Docker's image-based workflow, especially anything with frequent updates or complex dependency chains, run Docker inside an LXC or a lightweight VM instead of trying to replicate Docker's behavior natively in LXC.

The payoff is real. You get cleaner resource allocation, easier snapshots, more predictable behavior, and backups that actually restore cleanly. If your Proxmox setup feels janky, this reframe is probably the fix.

Next step: Read the full XDA walkthrough and audit which of your LXCs are fighting their own architecture.