WhisperX tag archive

#SBOM

This page collects WhisperX intelligence signals tagged #SBOM. It is designed for humans, search engines, and AI agents: each item links to a canonical source-backed record with sector, source, timestamp, credibility, and exportable structured data.

Latest Signals (16)

The Lab · 2026-03-27 14:27:28 · GitHub Issues

1. HVE Core Proposes VEX Workflow to Cut Vulnerability Noise, Signal Real Risk

A proposal to integrate a VEX (Vulnerability Exploitability eXchange) workflow into the HVE Core project aims to solve a critical signal-to-noise problem in software supply chain security. Currently, consumers and auditors receive only a Software Bill of Materials (SBOM), which lists all dependencies and flags every po...

The Lab · 2026-03-29 02:27:01 · GitHub Issues

2. GitHub Project Adds Supply Chain Security Analyst Agent to Automate Dependency & CI/CD Hardening

A new 'Supply Chain Security Analyst' agent has been added to a command-line tool's security component suite, targeting a critical gap in automated software defense. The agent is designed to perform comprehensive, ecosystem-specific security analysis across major development platforms, moving beyond basic vulnerability...

The Lab · 2026-03-31 15:27:18 · GitHub Issues

3. cdxgen Tool Detects npm Package Version Spoofing Vulnerability in Software Supply Chain

A critical vulnerability enabling npm package name and version spoofing has been detected in the wild, posing a direct threat to software supply chain security. The issue, detailed in a security blog, allows attackers to publish malicious versions of legitimate packages, potentially delivering remote access trojans. Th...

The Lab · 2026-04-01 11:27:15 · GitHub Issues

4. Vulnerability in `sbomqs` Command Execution: Missing `--` Separator Allows Option Injection via Filename

A critical vulnerability has been identified in the `sbomqs` command execution within the software supply chain security tooling. The flaw stems from a missing `--` separator and an unsafe argument order, which allows a maliciously named file to be interpreted as a command-line option. Specifically, the vulnerable code...

The Lab · 2026-04-01 16:27:21 · GitHub Issues

5. cdxgen SBOM Tool Vulnerability: Malicious .npmrc File Can Bypass `--ignore-scripts` and Execute Code

A critical security vulnerability has been identified in the cdxgen Software Bill of Materials (SBOM) generation tool, where a malicious `.npmrc` configuration file can trigger arbitrary code execution even when the `npm install` command is run with the `--ignore-scripts` safety flag. This bypass occurs during the tool...

The Lab · 2026-04-03 15:27:03 · GitHub Issues

6. SBOM Task Functions Contain Critical Path Traversal Vulnerability, Exposing Cross-Project File Access

A critical security vulnerability has been identified in four key SBOM (Software Bill of Materials) task functions within the codebase. The functions `generate_sbom`, `score_tool`, `score_attestation`, and `score_osv` directly use user-supplied `args.file_path` and `args.revision_number` to construct file system paths ...

The Lab · 2026-04-04 15:27:02 · GitHub Issues

7. GitHub CI Policy Shift: Auto-Registering 'Won't Fix' CVEs via OpenVEX to Bypass Manual Workflow Edits

A proposed change to a GitHub CI/CD policy workflow seeks to automate the management of permanently unfixable, high-severity vulnerabilities, eliminating the need for manual script edits with each new scan. The current process lacks a formal Vulnerability Exploitability eXchange (VEX) register, forcing developers to ma...

The Lab · 2026-04-04 15:27:03 · GitHub Issues

8. GitHub CI Policy Shift: OpenVEX File Automates 'Won't-Fix' CVE Suppression for High-Severity Vulnerabilities

A proposed change to a GitHub repository's CI/CD pipeline reveals a strategic move to automate the handling of unfixable, high-severity vulnerabilities. The current policy lacks a formal Vulnerability Exploitability eXchange (VEX) register, forcing developers to manually edit workflow scripts each time a permanently un...

The Lab · 2026-04-05 15:27:05 · GitHub Issues

9. CascadeGuard Actions: SBOM Generation & Supply Chain Scanning Mandate Hits Open Source

Open-source projects are now facing a direct compliance mandate. The push to integrate Software Bill of Materials (SBOM) generation and supply chain vulnerability scanning into development workflows is no longer optional, driven by binding requirements like NIST's Secure Software Development Framework (SSDF) and U.S. E...

The Lab · 2026-04-05 22:26:51 · GitHub Issues

10. AI-Gateway 项目夜间扫描警报:已部署制品中发现新的 HIGH+ 级别安全漏洞

GitHub 安全扫描工作流在已部署的制品中检测到新的 HIGH 或 CRITICAL 级别安全漏洞,触发了紧急警报。这一发现表明,即使代码已经完成构建和部署,其依赖项或容器镜像中仍可能存在未被及时发现的严重安全缺陷。警报明确指出,软件物料清单(SBOM)和容器镜像的重新扫描均返回了阳性结果,证实了漏洞的存在,而非误报。 此次事件涉及 theagenticguy 用户下的 ai-gateway 项目。系统在 2026 年 4 月 5 日的夜间例行扫描后,自动生成了包含具体工作流运行链接的警报。项目维护者被指示立即审查安全选项卡中的详细发现,对 HIGH 及以上级别的漏洞进行分级和修复,并可在本地运行 `mise run secur...

The Lab · 2026-04-06 07:27:04 · GitHub Issues

11. AI-Gateway 项目夜间扫描警报:已部署制品中发现新的 HIGH+ 级别安全漏洞

GitHub 的自动化安全扫描在已部署的制品中检测到新的高危漏洞,触发了紧急警报。此次夜间重新扫描工作流确认,在 theagenticguy/ai-gateway 仓库中,已投入使用的软件物料清单(SBOM)和容器镜像均存在被标记为 HIGH 或 CRITICAL 级别的安全缺陷。这表明,即使代码已通过初始审查并部署,其依赖项或构建产物中仍可能潜伏着新近被发现或引入的严重风险。 警报直接指向项目维护者,要求立即审查 GitHub 仓库安全选项卡中的详细发现,并对高危及以上级别的漏洞进行优先级排序和修复。工作流还提供了本地复现命令 `mise run security`,以便开发者在自己的环境中验证和定位问题。这一自动化流程的触发,...

The Lab · 2026-04-10 11:39:54 · GitHub Issues

12. JIM's SBOM Gap: Compliance Claims Weakened by Lack of Continuous Vulnerability Visibility

JIM's software supply chain security posture contains a critical operational gap. While the organization generates Software Bill of Materials (SBOMs) at release time for compliance reporting, it lacks continuous visibility into vulnerability drift in its main development branch. This means that between official release...

The Lab · 2026-04-14 10:22:41 · GitHub Issues

13. docker-hash CLI's Supply Chain Exposed: No Provenance, No Detection for Tampered Releases

The `docker-hash` tool, a critical dependency for countless CI/CD pipelines, currently ships its release artifacts with zero verifiable supply-chain security. As a CLI, Docker image, and GitHub Action, its compromised build process would directly infect every downstream consumer. There is no SLSA attestation, no SBOM, ...

The Lab · 2026-04-19 12:22:35 · GitHub Issues

14. Operate's Docker Images Lack SBOM, Creating Critical Supply Chain Blind Spot for Enterprises

Operate's CI/CD pipeline is shipping Docker images without a Software Bill of Materials (SBOM), creating a significant visibility gap for enterprise customers. This omission prevents security and procurement teams from verifying the third-party libraries and dependencies bundled inside the container images they deploy ...

The Lab · 2026-04-21 07:22:45 · GitHub Issues

15. GitHub Security Alert: Code-Context-Agent Repository Hit by New HIGH+ Vulnerabilities in Nightly Scan

A scheduled nightly security scan has flagged new, unaddressed vulnerabilities rated HIGH or CRITICAL within the `code-context-agent` repository. The automated workflow, triggered on April 7, 2026, confirms active findings from a Software Bill of Materials (SBOM) rescan, signaling the presence of exploitable weaknesses...

The Lab · 2026-04-21 07:22:46 · GitHub Issues

16. GitHub Security Alert: Nightly Rescan Flags New HIGH+ Vulnerabilities in CodeProbe Repository

A scheduled nightly security rescan has triggered an alert, detecting new vulnerabilities rated HIGH or CRITICAL within the CodeProbe repository. The automated workflow confirmed findings from a Software Bill of Materials (SBOM) analysis, indicating the presence of potentially exploitable weaknesses in the project's de...