Urgent.News

What's breaking now, across thousands of outlets.

Tech

The Encoded PSEMHUB Path That Broke CVE-2026-35273 WAF Defenses

The Encoded PSEMHUB Path That Broke CVE-2026-35273 WAF Defenses The renewed ShinyHunters campaign against CVE-2026-35273 showed how a control can look correct in a policy and fail in production. Mandiant observed requests with /%50SEMHUB/ instead of /PSEMHUB/ . The encoded character reached the vulnerable PeopleSoft servlet while string-based WAF rules missed the path. This detail matters beyond…

A new ShinyHunters campaign exposed a flaw in Oracle PeopleSoft's security measures, CVE-2026-35273. The vulnerability allows remote code execution without authentication. A security firm noticed requests with an encoded '/%50SEMHUB/' path that bypassed web application firewalls (WAFs). The % character in the URL caused issues for the WAFs, which inspected request targets before the application decoded them.

This discrepancy allowed attackers to reach the Environment Management Hub, a server that could execute code with PeopleSoft's service account privileges. The attack chain involved the Integration Gateway forwarding requests to a malicious server, then using administrative file operations to write a web shell. Defenders must consider encoding, normalization, and routing differences between the WAF, reverse proxy, and application server.

Oracle released a fix in June 2026, but affected products require thorough review, including WAF configurations and internal application server settings.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Linkup /research is async. Treating it as synchronous is the bug, in code and in the freeze case

If you ship agents, you have made this mistake: you called an async endpoint, got a pending status back, and then either blocked waiting for a result that was never coming on that call, or polled so hard you got rate-limited. Linkup's /research works like this, from the docs and the corpus skill.

  • Linkup /research returns ID and pending status immediately
  • Poll GET /v1/research/:id until completion or failure
  • Exponential backoff up to 10-second interval, max 1 request/sec

More from Thursday 19 November →