Skip to content
Artwork for Ship It Weekly - DevOps, SRE, Platform and Cloud Engineering News
Ship It Weekly - DevOps, SRE, Platform and Cloud Engineering News · Yesterday · 16 min

GitHub Blocks pull_request_target by Default, WordPress Update Race Exploited, Polymarket Drained via Hijacked DebugBear Script & Alpine's GitLab Upgrade Missed the Fix

This week on Ship It Weekly, GitHub will block pull_request_target in public repos by default from December 2, with brownouts on Mondays, November 9 and 16, 11 AM to 1 PM ET. A WordPress core update race (CVE-2026-119977) is on CISA's exploited list: during a full-package update, a fresh installer can sit for a moment at a public URL under wp-content/upgrade. A hijacked DebugBear script drained about $2.7 million from Polymarket users after DebugBear's DNS was compromised through its registrar. And Alpine Linux explains why upgrading GitLab didn't fix CVE-2026-97229 on its own image: the fix was a patch to Ruby. The thread: what actually ran, as opposed to what you think ran. A trigger that runs a fork's code with your secrets, an update that opens its own window, a script served by whoever controls the DNS, and a version number that said "fixed". In the lightning round: OpenSSH 10.6p2 fixes a password login bypass on musl builds with PAM off, which is how Alpine builds openssh-server; Debian and Ubuntu patch an APT package swap (CVE-2026-109518); and .NET 8 and 9 reach end of support on Tuesday, November 10. The human closer comes back to Alpine's "we cannot rule it out." If an attack hit you this week, could your logs prove it didn't work? Highlights • pull_request_target: what it runs, and what to check before Monday • WordPress: when keeping current is what opens the window • DNS, HTTPS and subresource integrity for third-party scripts • Registrar lock, MFA and alerts on DNS changes • Alpine: GitLab from your own image needs a fixed Ruby too • "No evidence" is only as good as the logs you kept Links pull_request_target blocked by default (GitHub): https://tsn.io/KwebM WordPress advisory GHSA-4w3m-c66w-69mg: https://tsn.io/1HGiK WordPress upgrade-window RCE (Wordfence): https://tsn.io/Pc6X2 Polymarket postmortem: https://tsn.io/rOc2M DebugBear on the registrar DNS compromise: https://tsn.io/4BjIg Polymarket losses and refunds (Hackread): https://tsn.io/qNhoe Alpine's GitLab security incident: https://tsn.io/GpNoR OpenSSH 10.6p2 release notes: https://tsn.io/dQHbG Alpine openssh-server advisory: https://tsn.io/lExh2 APT CVE-2026-109518 (Debian DSA-6607-1): https://tsn.io/LSjTb .NET 8 and 9 end of support: https://tsn.io/7NC5R This week's On Call Brief: https://tsn.io/XJLrm More episodes and show notes: https://tsn.io/NqkdP On Call Brief: https://tsn.io/Gpz2d LMGT Awards: https://tsn.io/lAERA

0:00 · Cold open-16:07

transcript

No transcript — this publisher did not publish one.

show notes

This week on Ship It Weekly, GitHub will block pull_request_target in public repos by default from December 2, with brownouts on Mondays, November 9 and 16, 11 AM to 1 PM ET. A WordPress core update race (CVE-2026-119977) is on CISA's exploited list: during a full-package update, a fresh installer can sit for a moment at a public URL under wp-content/upgrade. A hijacked DebugBear script drained about $2.7 million from Polymarket users after DebugBear's DNS was compromised through its registrar. And Alpine Linux explains why upgrading GitLab didn't fix CVE-2026-97229 on its own image: the fix was a patch to Ruby.

The thread: what actually ran, as opposed to what you think ran. A trigger that runs a fork's code with your secrets, an update that opens its own window, a script served by whoever controls the DNS, and a version number that said "fixed".

In the lightning round: OpenSSH 10.6p2 fixes a password login bypass on musl builds with PAM off, which is how Alpine builds openssh-server; Debian and Ubuntu patch an APT package swap (CVE-2026-109518); and .NET 8 and 9 reach end of support on Tuesday, November 10.

The human closer comes back to Alpine's "we cannot rule it out." If an attack hit you this week, could your logs prove it didn't work?

Highlights

• pull_request_target: what it runs, and what to check before Monday

• WordPress: when keeping current is what opens the window

• DNS, HTTPS and subresource integrity for third-party scripts

• Registrar lock, MFA and alerts on DNS changes

• Alpine: GitLab from your own image needs a fixed Ruby too

• "No evidence" is only as good as the logs you kept

Links

pull_request_target blocked by default (GitHub): https://tsn.io/KwebM

WordPress advisory GHSA-4w3m-c66w-69mg: https://tsn.io/1HGiK

WordPress upgrade-window RCE (Wordfence): https://tsn.io/Pc6X2

Polymarket postmortem: https://tsn.io/rOc2M

DebugBear on the registrar DNS compromise: https://tsn.io/4BjIg

Polymarket losses and refunds (Hackread): https://tsn.io/qNhoe

Alpine's GitLab security incident: https://tsn.io/GpNoR

OpenSSH 10.6p2 release notes: https://tsn.io/dQHbG

Alpine openssh-server advisory: https://tsn.io/lExh2

APT CVE-2026-109518 (Debian DSA-6607-1): https://tsn.io/LSjTb

.NET 8 and 9 end of support: https://tsn.io/7NC5R

This week's On Call Brief: https://tsn.io/XJLrm

More episodes and show notes: https://tsn.io/NqkdP

On Call Brief: https://tsn.io/Gpz2d

LMGT Awards: https://tsn.io/lAERA

links15

chapters

10 chapters