57 results for “SBOM”

List Grid

What you seeeverything

Recent Oldest Added A–Z

All types57 Articles33 Repos14 Threads3 Advisories2

More types3

Papers2 Write-ups2 Tools1

“SBOM”

x.comarticle🧠 AI

huiwenhan (@huiwenhan) on X

PRAXO-CORE 2.5.0 is a Go agent kernel that owns model calls, tool authorization, context, checkpoints, events and human-in-the-loop decisions, and leaves graph execution, memory storage and tenant policy to RHEOVELA or the host product. The release adds pkg/conformance, with checks for VFS, memory, sandbox, event, policy, model and tool contracts. It also adds stricter Windows path rejection and a plugin trust/SBOM handoff, and it states which adapters are only offline-tested.

GoOllamaModel Context Protocol+6

PRAXO-CORERHEOVELARHEOVELA-ee+4

agents, ai-infra· Added 27 Oct 2026, published 25 Oct 2026

endorlabs.comarticle🛡️ Security

Everything, everywhere, all at once… the week software broke | Endor Labs

Endor Labs roundup of the 20 to 21 October 2026 patch wave: eMudhra certificate authority keys that anyone can recover, PHP2Shell (CVE-2026-109618, CVE-2026-109619), Node2Shell (CVE-2026-111497) and malware in LiteLLM 1.107.0. It lists fixed versions (PHP 8.2.35 to 8.5.12, Node.js 22.23.4, 24.22.1, 26.12.1, LiteLLM back to 1.106.2) and explains why many separate trust-store copies each need updating. It closes with advice on triage, remediation and SBOM/VEX reporting.

PHPNode.jsLiteLLM+3

CVE-2026-109618CVE-2026-109619CVE-2026-111497+3

Supply Chain, AppSec· Published and added 24 Oct 2026

enisa.europa.euadvisory🛡️ Security

ENISA Technical Advisory for Software Bill of Materials

ENISA Technical Advisory for Software Bill of Materials (October 2026, TLP:CLEAR) is non-mandatory guidance for organisations, especially SMEs, starting SBOM adoption. It covers SBOM data models (CycloneDX, SPDX), a mapping of BSI TR-03183-2 fields to CISA minimum elements, lifecycle and CI/CD integration, an SBOM threat model, and security recommendations. It supports Cyber Resilience Act obligations but is not a legal interpretation.

SBOMCycloneDXSPDX

ENISAEU Cyber Resilience ActBSI TR-03183+4

Supply Chain, GRC· Added 23 Oct 2026

enisa.europa.euadvisory🛡️ Security

ENISA Technical Advisory for Software Bill of Materials

ENISA Technical Advisory for Software Bill of Materials is practical guidance on SBOM adoption for organizations, especially micro, small and medium enterprises and open-source stewards. It sets out an SBOM implementation architecture and data flows across a defined lifecycle, an indicative SBOM threat model with targeted risks, and measures for the SBOM ecosystem. It aligns with the ENISA Secure by Design and Default Playbook and supports Cyber Resilience Act compliance.

SBOM

ENISAEU Cyber Resilience ActENISA Secure by Design and Default Playbook

Supply Chain, GRC· Added 23 Oct 2026

aikido.devarticle🛡️ Security

Software supply chain security best practices for 2026

Aikido's guide to software supply chain security controls for 2026, tied to real incidents. It covers a 48-hour package cooldown, ignore-scripts, lockfile enforcement, SHA and digest pinning, scoped tokens, FIDO2, developer endpoint protection, extension allowlists, agent sandboxing, MCP server vetting, slopsquatting, signed SBOMs and rotation drills. Examples include the March 2026 axios compromise and the March 2025 tj-actions/changed-files attack.

npmpnpmGitHub Actions+3

tj-actions/changed-filesCanisterWormGlassWorm+7

Supply Chain, DevSecOps, AI Security· Added 22 Oct 2026, published 21 Oct 2026

x.comthread🛡️ Security

Mikko Laakkonen (@mikkolaakkonen) on X

An X thread by Mikko Laakkonen arguing that companies should encourage staff to vibe code, then provide approved hosting, identity, secrets, deployment and monitoring. It lists 200 application checks in 17 sections, from ownership and data flow through keys, authz, coding-agent isolation, appsec, SBOM and releases to recovery, runtime AI and handover. It adds 16 EU bonus checks on GDPR, NIS2, the Cyber Resilience Act (reporting from 11 Sept 2026, main duties 11 Dec 2027), the AI Act and the Data Act. It builds on Mark Ajzenstadt's production-readiness post and links a 300-check worksheet version.

LovableClaude CodeGrok+3

Mikko LaakkonenMark AjzenstadtGDPR+12

GRC, DevSecOps, AI Security· Added 18 Oct 2026, published 17 Oct 2026

endorlabs.comarticle🛡️ Security

Why Your SCA is Always Wrong | Endor Labs

Explains why traditional SCA tools are inaccurate: they parse package-manager manifests and assume those match what the code actually uses. It walks through phantom dependencies, misused dependency scopes, direct use of transitive dependencies and unused dependencies, using Python and JavaScript as examples. It argues for SCA based on program analysis, with source code as ground truth cross-checked against manifests and the file system. Useful for evaluating SCA tools and understanding SBOM accuracy limits.

PythonJavaScriptnpm+3

phantom dependenciestransitive dependenciesdependency scopes

Supply Chain, AppSec· Published and added 16 Oct 2026

endorlabs.comwriteup🛡️ Security

SBOM vs. SBOM: Comparing SBOMs from Different Tools and Lifecycle Stages | Endor Labs

Case study running three open source SBOM generators (two generic, one Maven plugin) on Eclipse Steady 3.2.5 rest-backend at three lifecycle stages (git clone, Maven package, Docker image), yielding 8 CycloneDX SBOMs. Compares precision/recall against the mvn dependency:tree ground truth and finds the Maven-integrated tool perfect (1.0/1.0) while generic tools miss versions, groupIds and transitive dependencies. It also shows PURL qualifier differences (e.g. type=jar, apt qualifiers) make SBOMs hard to compare, test dependencies are indistinguishable, and argues for an SBOM generator benchmark.

SBOMCycloneDXMaven+3

Eclipse SteadyPackage URLNTIA+3

Supply Chain· Published and added 16 Oct 2026

endorlabs.comarticle🛡️ Security

SBOMs are Just a Means to an End | Endor Labs

A critique of the state of SBOM adoption, written by a CISSP product manager at Endor Labs. It argues that the NTIA minimum elements and the SPDX and CycloneDX specs don't require a package URL (purl), so name and version alone can't tell a Maven log4j-core from an npm or cargo package of the same name. It also notes that no spec defines build time, which makes transitive dependency resolution unreliable, and that generation tools place the same data in different fields. It adds that vendors have mixed incentives to ship SBOMs and that practices are immature, and it calls on standards bodies to define required data per prioritized use case.

SBOMSPDXCycloneDX+1

Executive Order 14028NTIANTIA Minimum Elements for an SBOM+2

Supply Chain, GRC· Published and added 16 Oct 2026

endorlabs.comarticle🛡️ Security

EU Cyber Resilience Act: Preparing for December 11, 2027 | Endor Labs

Explains what applies on 11 December 2027 under the EU Cyber Resilience Act: Annex I Part I and II, Article 13 manufacturer duties, conformity assessment and CE marking. It covers classification by core functionality, the conformity routes per tier, and how "known exploitable vulnerability" is defined, including findings from your own tooling and AI analysis. It also covers the engineering obligations (per-build SBOMs with VEX, CVD policy, security.txt, signed updates, CSAF disclosure), the 10-year retention and support-period rules, and the product-family and legacy-modification reliefs. It closes with a checklist, and the Endor Labs product claims are vendor-sourced.

Endor LabsSBOMCycloneDX+1

EU Cyber Resilience ActImplementing Regulation (EU) 2025/2392Annex I+7

GRC, Supply Chain· Published and added 14 Oct 2026

endorlabs.comarticle🛡️ Security

Executive Order 14028 SBOM Requirements: What to Comply With and How | Endor Labs

Explains what Executive Order 14028 requires for SBOMs. It covers the NTIA Minimum Elements (seven data fields, automation support, practices and processes) and the SPDX, CycloneDX and SWID formats. It also covers who must comply and how OMB M-26-05 (January 2026) rescinded the standardized self-attestation mandate while agencies can still require SBOMs by contract. It then argues an SBOM is only a starting point and recommends adding reachability analysis, EPSS, VEX and safe-upgrade remediation. The last part promotes Endor Labs.

SBOMSPDXCycloneDX+1

Executive Order 14028NTIANIST+10

GRC, Supply Chain· Published and added 12 Oct 2026

aws.amazon.comarticle🛡️ Security

Quantum-resistant signing on AWS, Part 1: Build a software supply chain with ML-DSA

Part 1 of an AWS series showing how to build a quantum-resistant software supply chain with ML-DSA: ML-DSA keys in AWS KMS, an ML-DSA root/subordinate CA hierarchy in AWS Private CA, and IAM Roles Anywhere trust anchors for external build agents. It covers signing binaries (EXTERNAL_MU with OpenSSL 3.5), container images as OCI referrers via ORAS, and SBOMs wrapped in in-toto Statements bound to the artifact digest, plus verification, admission control, trust-store distribution, revocation and SCP guardrails. It frames the "forge later" threat and maps CNSA 2.0 (ML-DSA-87 only for NSS) and EU CRA deadlines to actions.

AWSAWS KMSAWS Private CA+3

ML-DSANIST FIPS 204CNSA 2.0+8

Supply Chain, DevSecOps, Cloud & Infra· Published and added 12 Oct 2026

endorlabs.comarticle🛡️ Security

Guide to Implementing Software Supply Chain Security | Endor Labs

Vendor-authored guide that defines a software supply chain as developers, code, dependencies, AI models, containers and CI/CD pipelines. It walks through program components: OSS governance, SAST vs reachability-based SCA, AI model security, SBOM/VEX (NTIA minimum elements, SPDX vs CycloneDX), secrets scanning, CI/CD hardening, and signing/attestation with Cosign/Sigstore. It cites figures such as 95% of vulnerabilities sitting in transitive dependencies and only 1% of SBOMs being fully NTIA-conformant. Each section closes with an Endor Labs product pitch, so treat the framing as vendor-flavoured. The fetched text was truncated, so the final attestation/provenance section was not seen.

Endor LabsSBOMCycloneDX+3

Executive Order 14028NISTCISA+15

Supply Chain, DevSecOps, Learning· Published and added 12 Oct 2026

endorlabs.comarticle🛡️ Security

Identifying and Tracking FedRAMP False Positives | Endor Labs

Explains how FedRAMP treats false-positive SCA findings, which still have to be tracked in the POA&M and ConMon. It covers the deviation request (DR) process, the SCA problems of scale and missing context (manifest-based inventories, with 88% of imported code unused), and 30–180 day remediation SLAs. It argues that only high-confidence, function-level reachability that holds from any source is likely to satisfy a 3PAO. It then describes how Endor Labs uses call-graph analysis, SBOM/VEX output and rescanning to document false positives.

Endor LabsSBOMVEX

FedRAMPPOA&MConMon+4

GRC, Supply Chain· Published and added 12 Oct 2026

x.comthread🛡️ Security

Dan Kornas (@DanKornas) on X

NuGuard is an open-source AI application safety and security toolkit for agentic AI systems, released under Apache 2.0. It unifies AI-SBOM generation, structural static analysis of the AI stack, and sandboxed adversarial red-teaming (100+ scenarios covering prompt injection, tool abuse, and data exfiltration) into a single CLI workflow, with an automated judge that scores findings by impact and provides remediation guidance.

SBOM

AI Security· Published and added 7 Oct 2026

eprint.iacr.orgpaper🛡️ Security

Randomness-Anchored Runtime Discovery of Cryptographic Operations on Linux Using eBPF

This IACR ePrint paper presents a Linux runtime cryptographic discovery system built on eBPF user-space probes that detects both classical and post-quantum (ML-KEM) cryptographic operations as they execute, complementing static binary/SBOM analysis with dynamic observation. It uses "randomness anchoring" — correlating observed key-generation/encapsulation randomness with subsequent crypto API calls in the same process — to raise detection confidence without adding false positives, reporting perfect precision/recall on classical and ML-KEM workloads, median detection latency of 28 μs, and 14–18% overhead on key-generation-bound workloads. A nine-application case study (drawn from/paired with QED datasets) compares static vs. runtime views and shows how eBPF probe coverage limits what can be observed, relevant to building a runtime cryptographic bill of materials for PQC migration compliance.

eBPFLinuxML-KEM+1

QED datasets

AppSec, GRC· Added 8 Oct 2026, published 5 Oct 2026

x.comthread🛡️ Security

When Models Turn Brutal

A vendor thread from ZeroShieldAI argues the patch window has collapsed because AI models can now find and weaponize vulnerabilities faster than defenders can fix them. It cites ZeroDayBench (success jumping from ~13% on blind zero-days to 78% once patch location is known), Aikido Security's benchmark where DeepSeek V4 Pro found 28 of 32 recent CVEs for about 98 dollars per run, a Unit 42 finding that 92% of AI-discovered flaws are logic bugs fuzzers miss, and a Hugging Face stat that 16 of the top 300 models advertise removed safety guardrails with 16.8M downloads. It promotes an attached 6-page case study and lists five defender recommendations: treat disclosure as exploit day, maintain SBOM/AIBOM, inventory models and agents, gate agent tool calls with policy, and red-team code and AI apps.

DeepSeekAikido SecurityHugging Face+1

ZeroDayBenchUnit 42

AI Security, Threat Intel· Published and added 1 Oct 2026

fossa.comarticle🛡️ Security

Generating and Managing C and C++ SBOMs

A FOSSA blog post explaining why C/C++ SBOMs built from manifest-parsing alone are incomplete, since the ecosystem lacks a centralized package manager and relies heavily on vendored (copy-pasted) source and code snippets. It covers concrete generation paths: Conan's built-in conan.tools.sbom CycloneDX generator, Yocto/OpenEmbedded's native SPDX output via the create-spdx class, process-based tracking for vendored code (third_party/vendor path flagging, manual audits), and the differing snippet-support capabilities of SPDX versus CycloneDX.

SBOMCycloneDXSPDX+3

Supply Chain· Added 1 Oct 2026, published 29 Sep 2026

github.comrepo🛡️ Security

git-pkgs — dependency history & supply-chain analysis for git repos

git-pkgs is a Go rewrite of a Ruby tool that adds a git subcommand for tracking dependency changes across a repository's history, indexing manifests/lockfiles from 36+ package managers (npm, RubyGems, Cargo, PyPI, Maven, Composer, Go modules, etc.) into a local SQLite database. Beyond history/blame/diff, it offers supply-chain security commands: `vulns` (OSV-based CVE scanning with SARIF output for GitHub code scanning, plus blame/praise/exposure for remediation metrics), `licenses` (with drift detection and CI-friendly exit codes), `deprecated`, `provenance` (trusted-publishing/attestation checks), `integrity` (lockfile hash drift detection), `maintainers`/`health` (via ecosyste.ms metadata), and `sbom` export in CycloneDX/SPDX. It also supports a dependency-aware `bisect` to find when a vulnerability, license change, or capability (e.g. network access) was introduced, and ships GitHub Actions for CI integration.

npmSBOMOSV+3

CVE-2024-1234PURL

Supply Chain, DevSecOps· Added 25 Sep 2026

arxiv.orgpaper🛡️ Security

Resource-Optimized and Energy-Aware Agentic AI Framework Anchored on Blockchain for Secure Software Supply Chains

This arXiv paper proposes a blockchain-anchored agentic AI framework for securing the software development lifecycle: specialized LLM-backed agents handle source integrity, SBOM/dependency analysis, CI configuration auditing, artifact verification, and runtime policy evaluation, each producing a cryptographically signed attestation recorded on a permissioned blockchain via smart contracts (agent registry, immutable attestation log, release-policy module). Agent-to-agent and agent-to-blockchain communication is secured through a consortium-operated certificate authority, and a sequence flow illustrates a source-code security agent anchoring its attestation on-chain to trigger an allow/block deployment decision. It's a conceptual architecture paper rather than an evaluated deployment, aiming to give decentralized, tamper-resistant provenance for agentic AI monitoring the software supply chain.

SBOMLLM

Supply Chain, AI Security, DevSecOps· Added 2 Oct 2026, published 25 Sep 2026

cloud.google.comarticle🛡️ Security

Proactive Defense: Hardening Code Pipelines and CI/CD Infrastructure

Mandiant's guidance for hardening the software supply chain across five pillars: endpoint, code repositories, artifact management, CI/CD and deployment. It covers a seven-day dependency cooldown, pinning images and actions by digest or commit SHA, ephemeral runners, OIDC short-lived tokens, build cache isolation, signed SBOMs, SLSA provenance and admission-time signature checks. It responds to campaigns using cache poisoning, OIDC token theft and mutable action tags.

GitHub ActionsOIDCSBOM+3

MandiantGitHub Actions cache poisoningPoisoned Pipeline Execution+4

DevSecOps, Supply Chain· Added 29 Oct 2026, published 24 Sep 2026

endorlabs.comarticle🛡️ Security

The UK Software Security Code of Practice through a Software Supply Chain Lens | Blog | Endor Labs

Endor Labs analyzes the UK's Software Security Code of Practice, a government-issued framework for software vendors, through the lens of software supply chain security. It breaks down how the Code's requirements map to practices like SBOM generation, dependency/component management, and vendor accountability for third-party code.

SBOM

UK Software Security Code of Practice

Supply Chain, GRC· Published and added 11 Sep 2026

endorlabs.comarticle🛡️ Security

Key Questions for Your SBOM Program | Blog | Endor Labs

Endor Labs blog post outlining six practical questions organizations should answer before standing up an SBOM program: how to send/receive/store SBOMs, which vendors must provide them (via business impact analysis), delivery frequency and SLAs, how to analyze them for exploitability (reachability analysis vs. simple CVE counting), remediation/risk-acceptance policy, and using SBOMs plus VEX during incident response (e.g., Log4Shell-style disclosures). It closes with a pitch for Endor Labs' source-code-based SBOM/VEX generation.

SBOMEndor Labs

Log4Shell

Supply Chain, GRC· Published and added 11 Sep 2026

endorlabs.comarticle🛡️ Security

Next-Gen SCA for C/C++: Closing the Detection Gap | Blog | Endor Labs

Endor Labs announces C/C++ language support for its SCA product, addressing the long-standing difficulty of tracking OSS dependencies in ecosystems with no central package registry. Because C/C++ developers commonly vendor (copy and modify) library source directly into their repos, Endor Labs builds a fingerprint index of known OSS libraries using cryptographic hashes for exact-match segments (functions, license blocks, etc.) and ML-generated code embeddings to catch renamed, reformatted, or lightly modified copies. The company reports customer benchmarks showing 81% fewer false negatives and 143% more true positives versus prior tooling for building SBOMs and detecting vulnerable/license-non-compliant code in C/C++ codebases.

Endor LabsCSBOM

Supply Chain· Published and added 11 Sep 2026

endorlabs.comarticle🛡️ Security

OSS Vulnerabilities And The Digital Operational Resilience… | Blog | Endor Labs

Endor Labs breaks down the EU Digital Operational Resilience Act (DORA), applicable to financial entities from January 2025, focusing on Article 9 (patch management) and Article 25 (open source analysis/source code review), plus the January 2024 Regulatory Technical Standards Articles 10 (tracking third-party/OSS libraries) and 16 (source code review, security testing before production). It then maps these compliance requirements to concrete AppSec practices: SBOM/SCA for component inventory, proactive OSS risk scoring, vulnerability scanning, and function-level reachability analysis to prioritize remediation and generate VEX documents, noting overlap with PCI DSS requirements 6.3/11.3.

Endor LabsSBOMEPSS

DORAPCI DSSGDPR

GRC, Supply Chain· Published and added 11 Sep 2026

endorlabs.comarticle🛡️ Security

How CycloneDX VEX Makes Your SBOM Useful | Blog | Endor Labs

Endor Labs explains how the CycloneDX Vulnerability Exploitability eXchange (VEX) format's analysis sub-field (state, justification, response, detail) lets software publishers communicate real exploitability of SBOM-listed CVEs, cutting through the noise of scanners that flag thousands of largely non-exploitable findings. It walks through each state value (resolved, resolved_with_pedigree, exploitable, in_triage, false_positive) as a machine-readable alternative to ad hoc spreadsheets/portals for vulnerability disclosure, referencing log4shell (CVE-2021-44228) as a case where faster communication would help.

CycloneDXSBOM

CVE-2021-44228

Supply Chain· Published and added 11 Sep 2026

endorlabs.comarticle🛡️ Security

SSDF Compliance and Attestation: A Practical Guide | Blog | Endor Labs

Endor Labs breaks down CISA's finalized Secure Software Development Attestation Form, which requires federal software suppliers to attest compliance with NIST's Secure Software Development Framework (SSDF) under EO 14028, with critical software due June 8, 2024 and other software due September 8, 2024. It covers the form's scope (excluding federal-developed, open source, and freely available software), flags ambiguous language and gaps (no explicit SBOM/threat-modeling/memory-safety mandate), and maps the four required practice areas — secure environments, trusted source code supply chains, code/artifact provenance, and vulnerability scanning/remediation — to Endor Labs' supply chain security platform features.

Endor LabsSBOM

NIST SSDFExecutive Order 14028CISA+3

GRC, Supply Chain· Published and added 11 Sep 2026

endorlabs.comarticle🛡️ Security

Demystifying Transitive Dependency Vulnerabilities | Blog | Endor Labs

Endor Labs blog post demystifying transitive dependencies — libraries pulled in indirectly through direct dependencies — and explaining why they complicate software composition analysis: multiple versions of the same transitive dependency can coexist in a project, it's harder to see what's actually used, and manually forcing an update is risky. It argues reachability analysis (statically stitching first-party call paths through to transitive library code) is the key tool for determining exploitability and for satisfying auditors under PCI DSS, FedRAMP, and EO 14028 SBOM requirements, and walks through a real example where langchain4j pulls a vulnerable JSON library transitively via Redis's jedis client, with the fix being to bump jedis rather than the JSON library directly.

Endor LabsRedisLangChain

Executive Order 14028PCI DSSFedRAMP

Supply Chain· Published and added 11 Sep 2026

endorlabs.comarticle🛡️ Security

What is VEX and Why Should I Care? | Blog | Endor Labs

Endor Labs explains VEX (Vulnerability Exploitability eXchange), the CISA-backed machine-readable format that lets software producers assert whether a vulnerability in a component actually affects their product, complementing SBOMs which only list components and versions. It walks through how VEX documents annotate exploitability (e.g., unreachable code), and describes how Endor Labs automates this by building a dependency callgraph via static analysis to determine reachability and auto-generate SBOM/VEX documents.

Endor LabsSBOMCVSS+1

CISA

Supply Chain· Published and added 11 Sep 2026

github.comrepo🛡️ Security

vet (SafeDep)

vet is an open-source CLI (from SafeDep) that scans package manifests, SBOMs, container images, and source repos across npm, PyPI, Maven, Go, RubyGems, Cargo, and Packagist to surface vulnerabilities, malicious packages, and license/quality issues. It cuts through CVE noise by analyzing actual code-usage evidence, queries SafeDep Cloud's threat-intelligence database for real-time malware detection (e.g. flagged packages like express-cookie-parser, eslint-config-airbnb-compat), and lets teams enforce security/license/OpenSSF-Scorecard policies as CEL expressions in CI/CD via SARIF/JSON/Markdown reporting.

npmPyPIMaven+3

MAL-2025-3541MAL-2025-4339MAL-2025-4029+2

Supply Chain, DevSecOps· Published and added 7 Sep 2026

github.comrepo🛡️ Security

ForgeGuardian

ForgeGuardian is an open-source (Apache 2.0) supply chain security scanner covering 9 package ecosystems (npm, PyPI, Go, Maven, RubyGems, Cargo, NuGet, Hugging Face, GitHub Actions) via 8 concurrent scan engines and 223+ built-in malicious-package detection signatures. It runs fully offline/local-first, offers a CLI (fgctl) and self-hosted SOC-style dashboard, generates CycloneDX/SPDX SBOMs, supports Sigstore keyless signing and provenance tracking, policy-as-code rules, dependency topology/attack-surface mapping, drift detection with auto-quarantine, and SARIF output for GitHub Actions CI integration, plus optional AI-powered advisory/patch-agent triage.

npmPyPIGo+3

Supply Chain, DevSecOps· Published and added 5 Sep 2026

github.comrepo🛡️ Security

cyanheads/osv-advisory-mcp-server

osv-advisory-mcp-server is an MCP server that queries the OSV.dev vulnerability database, offering single-package version checks, batch audits of up to 1000 {name, ecosystem, version} tuples for SBOM/lockfile triage, and full advisory record fetch by OSV ID (GHSA/PYSEC/RUSTSEC/GO/DSA/DLA/CVE prefixes). It surfaces CVE aliases, CVSS vectors, derived severity labels, and CWE IDs, and is designed to chain into a companion nist-nvd-mcp-server for CVSS base scores, EPSS probability, and CISA KEV status. It ships as a keyless, no-API-key tool runnable via STDIO or Streamable HTTP, with a public hosted instance and Bun/npx/Docker install paths.

Model Context ProtocolOSVBun+3

CISA KEVEPSSnist-nvd-mcp-server

Supply Chain· Added 1 Sep 2026

github.comrepo🛡️ Security

PackageGuard

PackageGuard is an open-source .NET CLI tool that scans NuGet, npm, pnpm and Yarn dependencies (direct and transitive) across a codebase, enforcing hierarchically-configured allow- and deny-lists for licenses, packages and versions. It scores each package's Legal, Security and Operational risk using signals like OSV vulnerability data, maintainer activity, package signing and release cadence, and can emit a CycloneDX or SPDX SBOM enriched with OSV vulnerability data, plus console, HTML and SARIF output for CI/GitHub code scanning. It's positioned as a free alternative to commercial supply-chain tools like Black Duck and Snyk.

NuGetnpmpnpm+3

Supply Chain, DevSecOps· Published and added 31 Aug 2026

aikido.devarticle🛡️ Security

Securing Docker images

Aikido Security's guide to hardening Docker images explains where container vulnerabilities come from (base OS layers like Debian/glibc that ship far more than an app needs), citing CVE-2023-4911 (Looney Tunables in glibc) and the xz-utils backdoor as cautionary examples for version-pinning decisions. It lays out hardening steps such as multi-stage builds, removing unused packages, non-root users, read-only filesystems, dropping Linux capabilities, pinning base images by digest, generating SBOMs, and signing/verifying images, then pitches Aikido Images, which backports CVE patches onto the same pinned base image version instead of forcing a migration to a new hardened distro.

DockerNode.jsDebian+2

CVE-2023-4911xz-utils

DevSecOps, Supply Chain· Added 3 Sep 2026, published 28 Aug 2026

github.comrepo🛡️ Security

vibecheck

vibecheck is a free, open-source, client-side scanner that checks apps built with AI code generators (Lovable, Bolt, v0, Cursor, Claude Code) for common security holes: exposed Supabase Row Level Security / Firebase rules, secrets embedded in the client bundle (Stripe/AWS/DB keys), missing security headers, exposed .env/.git/source maps, unauthenticated LLM proxy or MCP endpoints, and email/TLS misconfigurations. It also scans public repos for cross-tenant IDOR patterns, committed secrets, an OSV.dev supply-chain check, a Dockerfile lint, and generates a CycloneDX SBOM; a companion CLI (tenant-guard) adds a live Postgres cross-tenant isolation test as a CI gate. The project cites CVE-2025-48757 (170+ Lovable apps found with RLS disabled) as motivation.

SupabaseFirebaseOSV+3

CVE-2025-48757IDOR

AppSec, Supply Chain, Mobile Security· Published and added 27 Aug 2026

aikido.devarticle🛡️ Security

Software supply chain security requires decisions rather than defaults

Aikido Security argues that supply-chain security should be driven by deliberate decisions rather than defaulting to "always upgrade," using the xz-utils backdoor (versions 5.6.0/5.6.1, where CISA advised downgrading rather than patching) and the 2026 lodash 4.18.0 release (which broke the _.template code path within a day of shipping a fix for an arbitrary code injection vulnerability, forcing a deprecation back to 4.17.21 before the real fix landed in 4.18.1) as evidence that neither blind pinning nor blind upgrading is inherently safe. It advocates backporting specific CVE fixes onto already-running versions instead of forcing full upgrades, and treating SBOMs as continuously maintained baselines rather than one-time compliance artifacts, closing with a promotion of Aikido Libraries' backporting capability.

lodashAikido Security

xz-utilsCISA

Supply Chain, GRC· Added 3 Sep 2026, published 26 Aug 2026

blog.docsgpt.cloudwriteup🛡️ Security

DocsGPT Security Hardening Playbook

DocsGPT documents the security practices it adopted through GitHub's Secure Open Source Fund: a public STRIDE-based THREAT_MODEL.md, mitigations for its sandboxed AI code-execution feature (scrubbed env vars, NetworkPolicy blocking internal IPs and cloud-metadata to stop SSRF, off-by-default), a dependency-tree audit with SPDX SBOM export and Dependabot, and CI automation using custom CodeQL queries, Bandit, zizmor for GitHub Actions hardening, and secret scanning. It's a practical baseline playbook for maintainers dealing with high volumes of AI-authored PRs that can't all be manually reviewed.

CodeQLDependabotSBOM+3

STRIDEGitHub Secure Open Source FundUncle Bob Martin

DevSecOps, Supply Chain, AI Security· Published and added 15 Aug 2026

fossa.comarticle🛡️ Security

FOSSA: EU CRA Compliance Timeline

A FOSSA blog post laying out the EU Cyber Resilience Act's (Regulation (EU) 2024/2847) phased compliance timeline: it entered into force 10 December 2024, vulnerability/incident reporting obligations to ENISA and national CSIRTs (including a 24-hour early warning) begin 11 September 2026, and full Annex I conformity with CE marking is required by 11 December 2027. It details what manufacturers should prioritize at each stage — CVD policy, incident-response workflows, SBOM automation, secure-by-design defaults, and conformity assessment — and promotes FOSSA's free CRA Readiness Assessment tool.

FOSSASBOM

EU Cyber Resilience ActRegulation (EU) 2024/2847ENISA+2

GRC· Published and added 7 Aug 2026

github.comrepo🛡️ Security

npm-scan

npm-scan is a CLI supply-chain security scanner (@lateos/npm-scan) that inspects npm packages and lockfiles for behavioral attack patterns missed by npm audit/Snyk/Socket, including obfuscated payloads, credential stealers, eBPF kernel rootkits, memory-level OIDC token extraction, GitHub maintainer-account spoofing, and AI-platform-targeted key theft. It ships 23 detectors (D1-D25), validated against real campaigns like IronWorm and Miasma, and outputs SBOM (CycloneDX/SPDX) and SARIF for GitHub Security, plus a workflow to submit critical findings to CISA's VINCE with mandatory manual review. It's free (MIT) for individuals/OSS/evaluation, with paid commercial tiers ($799-$9,900/yr).

npmGitHub ActionsDocker+3

IronWormMiasmaCISA+1

Supply Chain, DevSecOps· Published and added 5 Aug 2026

github.comrepo🛡️ Security

Beetle

Beetle is an offline-first mobile application security platform that statically analyzes Android APKs and iOS IPAs (including Flutter and React Native apps), combining decompilation, taint analysis, secret/endpoint extraction, certificate and native-binary hardening checks, and CVE enrichment with explainable 'intelligence engines' (ownership, confidence, evidence selection, finding fusion) that correlate findings into evidence-backed attack chains. It maps results to OWASP MASVS/Mobile Top 10, provides source-level navigation, and exports SARIF, CycloneDX SBOM, and PDF reports, with optional (non-scanning) AI assistance via Claude, OpenAI, Gemini, DeepSeek, or local Ollama for explaining findings.

AndroidiOSDocker+3

Mobile Security, AppSec· Published and added 31 Jul 2026

github.comrepo🛡️ Security

hackingtool

hackingtool is a console launcher that bundles 215 curated security tools across 21 categories (recon, OSINT, wireless, phishing, forensics, post-exploitation) so users can install and run them without hunting down individual Git repos. Its newer AI layer maps plain-English goals to the right tool and exact command, plans multi-step objectives with confirmation gates, and drafts engagement reports, while emphasizing safe installs (pinned/SHA-256-verified downloads, no curl|bash, list-form subprocess calls, signed releases with SBOM) and refusing out-of-scope asks like DoS or mass-targeting. It also ships a non-interactive orchestrator (`--engagement`/`--pipeline`) that normalizes tool output into findings.json for red team, blue team, OSINT, bug bounty, and DFIR workflows.

PythonDockerOllama+1

Offensive Security, OSINT· Added 3 Sep 2026, published 31 Jul 2026

fossa.comarticle🛡️ Security

FOSSA: CISA Releases the 2026 SBOM Minimum Elements

FOSSA breaks down CISA's 2026 Minimum Elements for a Software Bill of Materials, the first major revision since NTIA's original 2021 baseline, produced with NSA, FBI, and 15 international agencies. The update roughly doubles required data fields, adding 10 new elements (SBOM Author Signature, SBOM Data Format Name/Version, Generation Context, Tool Name/Version, SBOM Version, Component Hash Value/Algorithm, and Component License) while renaming and clarifying existing fields (e.g., Supplier Name → Component Producer) and mandating full transitive-dependency coverage with no minimum depth, RFC 9557 timestamps, and dropping SWID in favor of SPDX/CycloneDX.

SBOMSPDXCycloneDX+1

CISANTIAExecutive Order 14028

Supply Chain, GRC· Published and added 31 Jul 2026

endorlabs.comarticle🛡️ Security

Best SBOM Tools in 2026, Compared | Blog | Endor Labs

Endor Labs' 2026 SBOM tooling comparison sorts five tools into three functional layers: open-source generators (Syft, cdxgen, Microsoft SBOM Tool) that produce SPDX/CycloneDX inventories, OWASP Dependency-Track for centralized SBOM storage and continuous monitoring, and Endor Labs' own SBOM Hub which adds function-level reachability analysis to cut CVE alert noise by a claimed 95%. It breaks down each tool's ecosystem coverage, format support, and trade-offs (e.g., Syft's lack of reachability, cdxgen's CycloneDX-only output, Dependency-Track's need for a database) and gives a decision framework for picking a tool by stack and maturity level.

Endor LabsSyftSBOM+3

Supply Chain· Added 3 Sep 2026, published 29 Jul 2026

wolfssl.comarticle🛡️ Security

wolfBoot 2.9.0

wolfSSL's release announcement for wolfBoot 2.9.0, an open-source secure bootloader for embedded systems, covering new hardware targets (STM32N6/U3/C5/G4/WBA, NXP LPC54S018M-EVK, Kinetis KL26, Xilinx Zynq-7000), new crypto features (RSA-PSS image signatures, hardware crypto-callback interface, multi-root-CA verification, pre-computed IDevID/DICE attestation), and continued security hardening from Fenrir fuzzing including bounded unauthenticated image sizes, memory-copy limits during updates, and fault-injection resistant integrity verification. It also adds an sbom Makefile target producing CycloneDX and SPDX output for CRA-readiness.

wolfBootwolfSSLwolfHSM+3

LMSXMSS

Hardware & RF· Published and added 25 Jul 2026

github.comrepo🛡️ Security

RAPTOR

RAPTOR is an autonomous offensive/defensive security research framework built on top of Claude Code that chains static analysis (Semgrep, Coccinelle, CodeQL), binary analysis (radare2, Frida, Z3-based exploit feasibility), LLM-driven multi-stage vulnerability validation, exploit PoC generation, and patch writing into a single workflow against source code or compiled binaries. It also includes an /sca supply-chain command that enriches dependency findings with OSV, CISA KEV, EPSS, and SSVC data and emits CycloneDX SBOMs, and sandboxes LLM-generated/untrusted code execution using Linux namespaces, Landlock, and seccomp. Authored by Gadi Evron, Daniel Cuthbert, Thomas Dullien (Halvar Flake), Michael Bargury, and John Cartwright, it ships 200+ custom static analysis rules and supports multi-model LLM analysis (Claude, GPT, Gemini, Ollama).

Claude CodeSemgrepCodeQL+5

Gadi EvronDaniel CuthbertThomas Dullien+2

AppSec, Offensive Security, AI Security, Supply Chain· Published and added 28 Jun 2026

fossa.comarticle🛡️ Security

FOSSA: Allan Friedman

Allan Friedman, former NTIA/CISA SBOM and VEX program lead, lays out practical VEX workflows for both software producers and consumers: tracking exposure via SBOM plus CVE/OSV feeds, doing reachability-based impact analysis, documenting and publishing determinations, and closing the loop as status changes. He compares the four VEX formats (CSAF, CycloneDX, SPDX 3.0, OpenVEX), ranks the five standard "not affected" justifications by how verifiable/trustworthy they are, and ties adoption to emerging regulatory pressure from the EU Cyber Resilience Act and FDA medical-device SBOM review.

SBOMCycloneDXSPDX+3

Allan FriedmanNTIACISA+4

Supply Chain, GRC· Published and added 27 Jun 2026

aikido.devarticle🛡️ Security

SBOMs in 2026: Everyone's generating them, no one's using them

Aikido Security's blog post recaps ENISA's SBOM Adoption State of Play 2026 report, a survey of 334 organizations (65% EU-based, 80% impacted by the Cyber Resilience Act). Key findings: most orgs now generate SBOMs at build time but rarely consume them for security (only 7% have closed the generation-to-usage gap), 39% never receive SBOMs from suppliers, 28% still use proprietary/non-standard formats instead of CycloneDX (44%) or SPDX (29%), and coverage of transitive dependencies remains weak even though most real-world vulnerabilities hide there. The piece then pitches Aikido's Syft-based SBOM generation, CycloneDX/SPDX export, supplier SBOM import, and Device Protection as ways to close these gaps ahead of the CRA's December 2027 deadline.

SBOMCycloneDXSPDX+2

ENISABSIEU Cyber Resilience Act

Supply Chain, GRC· Added 3 Sep 2026, published 10 Jun 2026

stepsecurity.ioarticle🛡️ Security

New in the Threat Center: Compromised Components, Now Available via API

StepSecurity added a GET /github/{owner}/threat-intel/incidents/{incidentId}/compromised-components API endpoint to its Threat Center, returning structured data (package ecosystem, version, severity, verified status) for OSS components tied to a detected supply-chain compromise incident. It's positioned as the automatable counterpart to existing Threat-Intelligence detection events (SIEM/Slack/webhook alerts), PR-level compromised-package checks, and the Secure Registry, letting teams pull exact affected packages/versions on demand to drive incident response and cross-check against their SBOM or lockfiles.

StepSecuritySIEMSBOM

tj-actions/changed-files

Supply Chain, Threat Intel, DevSecOps· Added 3 Sep 2026, published 9 Jun 2026

microsoft.comarticle🛡️ Security

Updating the taxonomy of failure modes in agentic AI systems: What a year of red teaming taught us | Microsoft Security Blog

Microsoft's AI Red Team releases v2.0 of its Taxonomy of Failure Modes in Agentic AI Systems, adding seven new categories — agentic supply chain compromise, goal hijacking, inter-agent trust escalation, computer-use-agent visual attacks, session context contamination, MCP/plugin abuse, and capability/architecture disclosure — drawn from 12 months of red team engagements against deployed agents. The post details operational findings (HitL bypass via consent fatigue was the most exploited failure mode, with several zero-click end-to-end exfiltration chains observed) and new mitigations spanning supply chain SBOMs for agent components, zero-trust cryptographic inter-agent identity, and hardened human-in-the-loop consent architecture. It also cites context driving the update, including OpenClaw's 512-vulnerability audit and CVE-2026-25253, and 99 MCP-related CVEs published in 2025.

Model Context ProtocolOpenClaw

CVE-2026-25253

AI Security· Added 1 Jul 2026, published 4 Jun 2026

github.comrepo🛡️ Security

CVE Lite CLI

CVE Lite CLI is an OWASP Lab Project CLI that scans npm, pnpm, Yarn, and Bun lockfiles against OSV and the npm advisory API and outputs copy-and-run fix commands instead of raw CVE lists, with parent-aware guidance for transitive dependencies. Beyond core CVE scanning it audits override/resolution hygiene, flags maintenance risk (deprecated direct deps and version drag blocking fixes), warns when a suggested fix falls inside a package manager's release-cooldown window (referencing the chalk/debug npm compromise), and emits SARIF, SPDX/CycloneDX SBOMs, and EPSS-based priority tiers, plus a GitHub Action that opens batched fix PRs.

npmpnpmYarn+3

chalk

Supply Chain, DevSecOps· Published and added 31 May 2026

socket.devarticle🛡️ Security

Socket: OSV Withdraws 157 Malware Reports

OSV, the OpenSSF-backed vulnerability database, withdrew 157 malicious-package reports on May 26 after automated detections from Amazon Inspector incorrectly flagged trusted npm and PyPI packages — including FastAPI, Strawberry GraphQL, and @tanstack/start-storage-context — as malware. The FastAPI record (MAL-2026-4750) claimed the package added a "typosquat-shaped" dependency (fastar) but never identified an actual malicious payload; OpenSSF paused the Amazon Inspector ingestion pipeline after the rollback. Because OSV feeds scanners, SBOM tools, registry controls, and CI/CD gates, the bad records had already propagated and forced maintainers to prove their packages were not compromised.

OSVnpmPyPI+1

FastAPIMAL-2026-4750Amazon Inspector+11

Supply Chain· Published and added 28 May 2026

osv.devtool🛡️ Security

OSV

OSV.dev is an open, distributed vulnerability database using the OpenSSF OSV schema to describe vulnerabilities precisely mapped to package versions or commit hashes, aggregating sources like GitHub Security Advisories, PyPA, RustSec, and the Global Security Database. It provides a free query API (by commit hash or package version) and the OSV-Scanner CLI/GitHub Actions workflows to scan SBOMs, lockfiles, container images, and repositories for known vulnerabilities, with an experimental `fix` command for automated remediation.

OSVGitHub ActionsDocker+3

CVE-2022-27651

Supply Chain, DevSecOps· Added 3 Sep 2026, published 25 May 2026

github.comrepo🛡️ Security

OWASP/DockSec

DockSec is an OWASP Lab Project CLI that wraps Trivy, Hadolint, and Docker Scout to scan Dockerfiles, images, and Compose files, then uses an AI provider (OpenAI, Anthropic, Google, or local Ollama) to correlate findings, cut noise, and generate plain-English remediation suggestions. It supports CI/CD gating via exit codes, baselines, and auditable waiver files, outputs SARIF/CycloneDX SBOM/HTML/PDF/JSON/CSV/Markdown reports, and redacts secrets before any content reaches an LLM, with a fully offline/local-only mode for air-gapped teams.

DockerTrivyHadolint+3

CVE-2023-45853

DevSecOps· Published and added 14 May 2026

labs.cloudsecurityalliance.orgarticle🛡️ Security

CSA: VulnOps in the Age of AI

Cloud Security Alliance research note arguing that traditional vulnerability management (scan, ticket, patch on a calendar) is breaking under AI-driven vulnerability discovery volume, NVD's April 15, 2026 risk-based triage policy that limits full CVE enrichment to CISA KEV/EO 14028/federal-use software, and compressed disclosure-to-exploitation windows. It defines VulnOps as a flow-oriented operating discipline (borrowing SRE/DevOps metrics like lead time, change-failure rate, and pipeline saturation) built on continuous discovery, EPSS/KEV-based risk prioritization instead of CVSS-only ranking, automated remediation-as-code, and first-class SBOM/supply-chain visibility, while also flagging agentic AI itself (prompt injection, tool-poisoning, MCP command execution) as a new vulnerability class the practice must cover.

NVDCVSSEPSS+2

Big SleepDARPA AI Cyber ChallengeExecutive Order 14028+9

GRC, AI Security, Supply Chain· Added 3 Sep 2026, published 13 May 2026

socket.devarticle🛡️ Security

Socket: pnpm 11 Adds Supply Chain Protection Defaults

Socket covers pnpm 11's new security-by-default settings: a 24-hour Minimum Release Age that delays resolution of freshly published package versions, blockExoticSubdeps which by default rejects transitive dependencies resolved from git/tarball URLs instead of the registry, and a new allowBuilds model that consolidates prior build-script controls (onlyBuiltDependencies, ignoreDepScripts, etc.) into a single package-pattern-to-boolean map. The piece ties these defaults to the conditions exploited by the Mini Shai-Hulud campaign (npm/PyPI/Packagist compromise using preinstall hooks to fetch a Bun runtime and run a credential stealer), and also notes pnpm 11's built-in SBOM generation (CycloneDX 1.7/SPDX 2.3), GHSA-based audit --fix=update, and a preview of the Rust-based Pacquet install engine slated for pnpm v12.

pnpmnpmCycloneDX+3

Mini Shai-HuludPacquet

Supply Chain· Published and added 7 May 2026

github.comrepo🛡️ Security

CRA Compliance Lab

CRA Compliance Lab is a GitHub organization hosting tooling and curated resources for EU Cyber Resilience Act (Regulation 2024/2847) compliance, including cra-sbom-cli — a local CLI that pre-flights CycloneDX or SPDX SBOM files against CRA-aligned content checks and outputs a PDF report — plus an awesome-list covering the regulation, harmonised standards, EUCC, and vulnerability management, and forks of sbomqs and the ENISA Secure by Design/Default playbook. It matters as one of the few practical, hands-on toolsets for organizations operationalizing CRA SBOM and secure-by-design requirements rather than just discussing the law.

CycloneDXSPDXPython+1

EU Cyber Resilience ActENISA

GRC, Supply Chain· Published and added 6 May 2026

github.comrepo🛡️ Security

CRA SBOM CLI

cra-sbom-cli is an offline Python CLI that reads a CycloneDX or SPDX SBOM and runs automated content checks derived from the EU Cyber Resilience Act (Regulation (EU) 2024/2847), prEN 40000-1-3:2025, and BSI TR-03183-2 v2.1.0, producing a terminal summary plus a detailed PDF report with a manual-evidence catalogue for auditors. It bundles (and must be kept in sync with) the compliance logic of a separate "CRA SBOM Platform" backend, optionally enriches results with grype/sbomqs, and supports CI gating via JSON verdict output; it explicitly flags that a PASS verdict alone does not equal CRA conformity since some requirements need manual evidence.

CycloneDXSPDXPython

EU Cyber Resilience ActprEN 40000-1-3:2025BSI TR-03183-2

GRC, Supply Chain· Published and added 6 May 2026