CyberPulse · Edition No. 125 · Wednesday, September 23, 2026

Approved Without You

Authority is being granted without human approval: forged tokens that pass as administrators, pre‑auth workflow execution, a handset baseband zero‑click, a web chain that turns a single URL into server access, and fresh exploited‑in‑the‑wild edge items — translated into immediate containment and governance actions.

Operational Threat Intelligence

CyberPulse editorial cover image for Approved Without You

Confidence High

Published 2026-09-23

Primary signal Validators and evaluators — the mechanisms that say yes — are being bent so that approval happens without you.

Why it matters Authority is being granted without human approval: forged tokens that pass as administrators, pre-auth workflow execution, a handset baseband zero-click, a web chain that turns a single URL.

Executive signal

Decision systems are being impersonated. Validators and evaluators — the mechanisms that say yes — are being bent so that approval happens without you.

API token verification accepting unsupported algorithms can mint administrator‑level access — lock algorithms to an allowlist and rotate keys exposed through the API fabric.

Workflow engines reachable pre‑auth must disable unsafe evaluators and remove host access — otherwise one HTTP call becomes operating‑system control.

Baseband‑adjacent handset exploitation removes user intent — move privileged approvals off devices that cannot attest device and session state.

A crafted theme‑preview URL can escalate into server‑side code execution — review extensions in a sandboxed profile or tenant, not in a privileged session.

What changed today

Across the region, the quiet middle layers of trust are being targeted: JSON Web Token validators, inline evaluators inside workflow platforms, theme‑install paths, and router services at the edge. Several items moved from theoretical to observed: forged administrator tokens hitting honeypots, unauthenticated workflow execution used for command‑and‑control staging, environment‑variable sweeps focused on cloud and model secrets, and proximity‑based handset elevation confirmed as active and targeted.

Immediate actions

P0 — Identity & API Gates (Do now)

Turn validators into deniers by default

Enforce strict JWT algorithm allowlists; reject anything outside the list. Rotate tokens and keys that could have been read through API backends. Bind auto‑quarantine to exposure signals so rotation, session kill, and pipeline freeze happen together.

P1 — Workflow & Low‑Code (This week)

Remove host access; require human‑in‑the‑loop

Disable unsafe evaluators; sandbox or containerize evaluation; forbid filesystem and subprocess access. Any change path touching credentials, pipelines, or network segmentation must require explicit human approval.

P2 — Mobile & Web Operations (This week)

Raise device baselines; isolate admin browsing

Move privileged approvals off endpoints without device and session attestation. Enforce minimum OS versions. Review themes/plugins in a non‑privileged browser profile or review tenant; block forced‑install primitives from reaching production.

Operational notes

API edge. A gateway flaw allows tokens signed with unsupported algorithms to pass as valid, granting wide access. Treat this as a breach of the approval system.

Workflow execution. Unauthenticated remote code execution via inline definitions converts evaluation into control. Remove host access and gate all privilege‑creating paths.

Developer tooling. Active probing against AI orchestration and web‑framework storage paths seeks cloud keys and model tokens. Lock down environment exposure and secrets handling.

Management plane. A maximum‑severity authentication bypass in an identity controller reinforces that control surfaces must assume hostile inputs at their edges.

Mobile proximity. A modem‑layer elevation under targeted use removes user interaction; approvals should not depend on unproven endpoints.

Edge devices. Recent exploited‑in‑the‑wild additions include widely deployed routers. Inventory and remediate exposed versions first.

Sign‑off — Wednesday, September 23, 2026 — Approved Without You

Sources

The Hacker News — Active Exploitation Attempts Target WSO2 API Manager JWT Bypass — https://thehackernews.com/2026/09/active-exploitation-attempts-target.html
The Hacker News — Critical Pre‑Auth RCE in Orkes Conductor Workflow Platform Exploited in the Wild — https://thehackernews.com/2026/09/critical-pre-auth-rce-in-orkes.html
The Hacker News — Attackers Exploit Critical Langflow and Rails Flaws — https://thehackernews.com/2026/09/attackers-exploit-critical-langflow-and.html
The Hacker News — Weekly Recap: Cisco Auth Bypass; Brevo Worker Supply‑Chain Injection; AI Agent RCE — https://thehackernews.com/2026/09/weekly-recap-cisco-0-day-ai-agent-rce.html
Cyber Security News — Android Pixel 0‑day Actively Exploited — https://cybersecuritynews.com/android-pixel-zero-day
Cyber Security News — Click2Shell WordPress Flaw Enables RCE With a Single Link — https://cybersecuritynews.com/click2shell-wordpress-vulnerability
The bloc's cybersecurity service — KEV: MikroTik RouterOS Additions — https://www.cisa.gov/news-events/alerts/2026/09/10/cisa-adds-two-known-exploited-vulnerabilities-catalog
The bloc's cybersecurity service — KEV: Chromium V8 Type Confusion — https://www.cisa.gov/news-events/alerts/2026/09/04/cisa-adds-one-known-exploited-vulnerability-catalog

Takeaways

Board takeaway in 20 seconds

Authority is being granted without human approval: forged tokens that pass as administrators, pre‑auth workflow execution, a handset baseband zero‑click, a web chain that turns a single URL into server access.
Trusted systems are now business attack surfaces; directors should ask where authority has been delegated and what evidence proves it is constrained.

What should CISOs do?

Identity & API Gates (Do now)
Inventory every agent, bot, workflow, script, and plugin that can read secrets, change code, trigger builds, or alter production settings.
Reduce delegated authority: least privilege for automation tokens, human approval on high-impact workflow actions, and emergency kill switches for agentic tools.

What should boards demand?

Workflow & Low‑Code (This week)
Mobile & Web Operations (This week)
A current map of which automated systems can change production code, infrastructure, identity permissions, or customer-facing content.

What should risk committees rethink?

Expand the risk register to include internet-, vendor-, and contractor-reachable operational systems that sit outside normal IT change control.
Require incident scenarios for harmful automated decisions: what instruction, data, credential, and approval path would investigators need to reconstruct?
Move assurance from vendor-by-vendor review to authority-chain review: who can act, through which tool, with which credential, and under whose risk acceptance.

The board blind spot is delegated authority. Security reviews still focus on individual systems, while the real exposure is increasingly in the control planes, automations, agents, and credentials that can change many systems at once. Directors should ask who can act through these layers, what evidence proves those actions are constrained, and how quickly harmful authority can be revoked.

Sources

CyberPulse · Signal over noise · Edition No. 125 Home