Continue reading the full briefing.
What to verify: Trace untrusted input through pull requests and jobs, review token scope, isolate runners, pin trusted dependencies, and rebuild affected artifacts after remediation.
Operational focus: Reduce persistent credentials and keep build jobs isolated from production management paths.
Open the original GitHub Advisory Database record
Disrupting supply chain attacks on npm and GitHub Actions
Explore the changes we've shipped across npm and GitHub Actions over the past few months to disrupt supply chain attack techniques and limit their impact. The post Disrupting supply chain attacks on npm and GitHub Actions appeared first on The GitHub Blog.
Why it matters: GitHub Security Blog participates in the path from source code to production. A weakness can inherit runner permissions, build secrets, trusted artifacts, or deployment access.
What to verify: Trace untrusted input through pull requests and jobs, review token scope, isolate runners, pin trusted dependencies, and rebuild affected artifacts after remediation.
Operational focus: Identify whether untrusted repository content can reach privileged runners, tokens, or deployment tools.
GitHub restructures public and VIP bug bounty payouts
GitHub says reports submitted from July 27 use a new static public payout table, while qualified VIP researchers receive higher rates and closer program access.
Why it matters: GitHub Bug Bounty Program participates in the path from source code to production. A weakness can inherit runner permissions, build secrets, trusted artifacts, or deployment access.
What to verify: Trace untrusted input through pull requests and jobs, review token scope, isolate runners, pin trusted dependencies, and rebuild affected artifacts after remediation.
Operational focus: Check dependency reachability and fixed versions before blocking or approving a release.
USN-8615-2: Linux kernel (Raspberry Pi) vulnerabilities
It was discovered that a logic flaw existed in the XFRM ESP-in-TCP subsystem in the Linux kernel when handling socket buffer fragments. This flaw is known as Fragnesia. A local attacker could use this to escalate privileges, or possibly escape a container. (CVE-2026-43503) Several security issues were discovered in the Linux kernel. An attacker could possibly use these…
Why it matters: Ubuntu Security Notices may be embedded across servers, containers, appliances, and administration hosts. Package installation alone does not prove that the corrected code is running.
What to verify: Compare distribution package versions, identify the loaded kernel or library, plan required service restarts or reboots, and validate workload health after the change.
Operational focus: Reduce persistent credentials and keep build jobs isolated from production management paths.
skilo add follows symbolic links, allowing arbitrary local file disclosure from a malicious skill source
### Impact `skilo add` installs a skill by recursively copying the skill directory into the target skills directory. The copy routine (`copy_dir_all`) classified each entry with `std::fs::DirEntry::file_type()` — which does **not** follow symlinks — and then copied non-directory entries with `std::fs::copy()`, which **does** dereference symlinks. As a result, a skill containing a symbolic link such as `reference.txt ->…
Why it matters: GitHub Advisory Database skilo participates in the path from source code to production. A weakness can inherit runner permissions, build secrets, trusted artifacts, or deployment access.
What to verify: Trace untrusted input through pull requests and jobs, review token scope, isolate runners, pin trusted dependencies, and rebuild affected artifacts after remediation.
Operational focus: Identify whether untrusted repository content can reach privileged runners, tokens, or deployment tools.
CVE-2026-54658: @hypequery/clickhouse has SQL Injection in parameter escaping that allows arbitrary SQL execution
### Impact A SQL injection vulnerability exists in the `escapeValue()` function used for parameter substitution. Attackers who can control parameter values can inject arbitrary SQL by using a trailing backslash to escape the closing quote. Who is impacted: All users of @hypequery/clickhouse versions prior to 2.0.2 who pass user-controlled input as query parameters. ### Patches The vulnerability has…
Why it matters: GitHub Advisory Database @hypequery/clickhouse participates in the path from source code to production. A weakness can inherit runner permissions, build secrets, trusted artifacts, or deployment access.
What to verify: Trace untrusted input through pull requests and jobs, review token scope, isolate runners, pin trusted dependencies, and rebuild affected artifacts after remediation.
Operational focus: Check dependency reachability and fixed versions before blocking or approving a release.
DevSecOps response plan
Protect the path from source code to production. Review what untrusted input can reach, which identities a runner can use, and whether secrets survive in logs, caches, or artifacts.
- Review current GitHub advisories against dependencies used by builds and internal services.
- Protect pull-request workflows from untrusted code execution and over-scoped tokens.
- Rotate secrets exposed in logs, artifacts, caches, or compromised runner workspaces.
- Use reviewed branches, isolated runners, pinned actions, and least-privilege deployment identities.
- Validate container base images and package lock files after security updates.
Build and release signals
Review trust boundaries at pull requests, runners, package resolution, artifact storage, credentials, and deployment approval.
- Identify whether untrusted repository content can reach privileged runners, tokens, or deployment tools.
- Check dependency reachability and fixed versions before blocking or approving a release.
- Reduce persistent credentials and keep build jobs isolated from production management paths.
Release decision
The secure release path minimizes inherited trust: isolated runners, short-lived identities, reviewed dependencies, reproducible artifacts, and explicit production approval.
References used in this briefing
- GitHub Advisory Database: CVE-2026-54650: openhole-server vulnerable to path traversal via URL-decoded request path
- GitHub Advisory Database: CVE-2026-54691: datamodel-code-generator vulnerable to SSRF via –url: no host/IP validation, follows redirects
- GitHub Advisory Database: CVE-2026-50567: Fission: Zip Slip in pkg/utils/zip.go:Unarchive allows fetcher to write outside the destination directory
- GitHub Security Blog: Disrupting supply chain attacks on npm and GitHub Actions
- GitHub Security Blog: GitHub restructures public and VIP bug bounty payouts
- Ubuntu Security Notices: USN-8615-2: Linux kernel (Raspberry Pi) vulnerabilities
- GitHub Advisory Database: skilo add follows symbolic links, allowing arbitrary local file disclosure from a malicious skill source
- GitHub Advisory Database: CVE-2026-54658: @hypequery/clickhouse has SQL Injection in parameter escaping that allows arbitrary SQL execution
Related briefings
Live DevOps Security Brief for July 28, 2026: Pipelines, Dependencies, and Secrets
Live DevSecOps coverage for build systems, source control, dependencies, automation agents, containers, and credential exposure. Updated for July…
Read More
Live DevOps Security Brief for July 27, 2026: Pipelines, Dependencies, and Secrets
Live DevOps Security intelligence for July 27, 2026, verified from current public advisories and official security feeds. Top…
Read More
DevOps Security Brief for July 23, 2026: Pipelines, Secrets, and Build Dependencies
A daily DevOps security review for CI/CD secrets, package advisories, runners, and build isolation.
Read MoreNeed to add context to this briefing?
Send corrections, security tips, source updates, or collaboration notes through the contact page so the editorial team can review them properly.