Attackers send X-GPUStack-Real-IP: 127.0.0.1 to gain admin on GPUStack
CVE-2026-102895 gives unauthenticated administrator access in GPUStack before 2.2.0, through a forged header or simply a same-host reverse proxy; SANS sees exploit attempts.
Contributing writer
Writes for Dev News Daily on the parts of software work that are not code: process, release discipline and what teams actually do with a change.
CVE-2026-102895 gives unauthenticated administrator access in GPUStack before 2.2.0, through a forged header or simply a same-host reverse proxy; SANS sees exploit attempts.
Three items from 12 to 14 November turn on a default value, and each shows a different way to change one without breaking the people who relied on the old behaviour.
Pay-as-you-go customers set a cap and alert thresholds per product; once the cap is hit, new billable invocations are rejected until the limit is raised, the policy removed or the billing cycle ends.
The new Full X policy discloses bugs X days after the report regardless of fix status: 90 days now, 60 from 2 February 2027 and 30 from 3 January 2028, with grace periods and variant rules removed.
A new repository_scan setting on the code scanning AI Scan endpoints works like the existing pr_scan: organisations set it, repositories inherit and can opt out, and enabling it does not start a scan.
A central team can own and rotate a secret while consuming accounts get an always-current local copy, without shared KMS keys or cross-account secret policies; replicas can be promoted.
Three notices from 10 to 13 November replace case-by-case judgement with a rule that can be checked by a machine, and each one moves work to the people downstream.
JetBrains lists the everyday changes behind the headline features: better generic inference, a pycharm: ignore comment, Zuban as a fourth external type checker and completion for Mock(spec=...).
The 12 November release also brings DropGuard, mem::conjure_zst, Cargo warnings for unused dependencies and a reorganised build directory to stop cache collisions.
The retirement follows the end of node20 support, because Node 24 has no ARM32 build; native AArch32 user-space execution on hosted runners goes too.