Skip to content

Standard

SBOM

A software bill of materials is a structured, machine-readable inventory of a software product's components and dependencies, used to assess supply-chain risk.

Known aliases

  • container SBOM
  • machine-readable SBOM
  • PBOM
  • pipeline bill of materials
  • SBOM
  • SBOMs
  • software bill of materials
  • software bills of materials

Current stories

securityOne report1 publisher

OmniTrust's Sequino says the QScan takedown leaves the hijackable edge devices in place

The DOJ and FBI pulled down two platforms a commentary attributes to Chinese state-sponsored operators. The same piece argues the routers and gateways recruited into those relays are still deployed and still weakly governed.

Publishers:scworld.com

Reality

Evidence20
Adoption
Not scored
Hype gap+35
Incentives80
Confidence55
buildOne report1 publisher

Buildpacks move the base image choice out of every application repository

In an account from The New Stack, a patched runtime image still misses production a week later because every service builds its own way, and buildpacks are offered as the shared path that closes the gap.

Publishers:thenewstack.io

Reality

Evidence32
Adoption
Not scored
Hype gap+28
Incentives
Not scored
Confidence44
leadershipOne report1 publisher

More than half the Windows VPN apps in a TechRadar audit shipped year-old open source code

Writing in Forbes, OpenVPN chief executive Francis Dinha names Turbo VPN and VyprVPN among providers found on a 2019 build and puts the exposure in what vendors did with the code after they took it.

Publishers:forbes.com

Reality

Evidence27
Adoption30
Hype gap+35
Incentives85
Confidence45
securityOne report1 publisher

Six ACM authors put the open-source bottleneck on the maintainers judging AI output

Six authors writing for the ACM's Technology Policy Council say AI has made code and vulnerability reports cheap to produce while the people who decide what ships are volunteers at projects like Apache, whose 2024 revenue was $2,379,402.

Reality

Evidence55
Adoption20
Hype gap+10
Incentives60
Confidence55
productOne report1 publisher

Exploitability depends on five links spread across six systems

A devops.com architecture piece traces the chain from package to executed code and keeps the model on interpreting what the traversal returns. Its test is whether a finding survives the model provider being unavailable.

Publishers:devops.com

Reality

Evidence52
Adoption
Not scored
Hype gap+15
Incentives
Not scored
Confidence45
productOne report1 publisher

September 11 puts a 24-hour clock on knowing what software actually shipped

The EU Cyber Resilience Act starts the notification clock the moment a manufacturer learns a flaw is being exploited, making SBOM accuracy an operational deadline as much as a compliance requirement.

Publishers:thenextweb.com

Reality

Evidence28
Adoption
Not scored
Hype gap+35
Incentives82
Confidence52
securityOne report1 publisher

Approving one coding agent doesn't cover what's installed inside it

Skills, hooks, repository instruction files and MCP servers all steer what an agent reads and runs, and governance that records only the application name leaves no inventory of the third-party code shaping builds.

Reality

Evidence38
Adoption
Not scored
Hype gap+32
Incentives58
Confidence47
securityOne report1 publisher

CISA asks buyers to make eliminated vulnerability classes a contract condition

Its review of fiscal 2024 and 2025 says opportunistic scanning of known, internet-exposed flaws drove most compromises. The fix, it argues, belongs to software producers, not to defenders patching faster.

Reality

Evidence58
Adoption18
Hype gap+15
Incentives55
Confidence55
securityOne report1 publisher

Cisco and VAIL fingerprint Nemotron models back to their Qwen base weights

Two fingerprinting methods recovered Qwen ancestry in Nemotron models that had been post-trained and republished under another name, which is why a rule that reads the publisher label cannot see what is in the weights.

Publishers:securityweek.com

Reality

Evidence38
Adoption15
Hype gap+22
Incentives68
Confidence45
productOne report1 publisher

Minimus's wind-down makes the hardened base image a continuity line item

Echo picked up the assets after Minimus decided to close, so this time the customers have somewhere to land. Anyone pinning a base image to one publisher is buying that publisher's rebuild queue too.

Publishers:siliconangle.com

Reality

Evidence40
Adoption
Not scored
Hype gap+32
Incentives78
Confidence42
productOne report1 publisher

Red Hat's hardened images now scan in AWS native tooling. Note what ECR Basic looks at

Support is live in the InspectorScan API and ECR Basic scanning, according to Red Hat. The registry scanner covers operating system packages, which is most of what a distroless image no longer has.

Publishers:redhat.com

Reality

Evidence28
Adoption20
Hype gap+38
Incentives88
Confidence34
securityOne report1 publisher

AI supply chain incidents are still bad packages and unwatched build pipelines

A vendor CEO says poisoned weights and hostile MCP servers remain demo material, while attackers register the package names your coding assistant invents.

Reality

Evidence24
Adoption
Not scored
Hype gap+15
Incentives80
Confidence33
buildOne report1 publisher

The useful number in IBM's 2026 breach report is 56%, not $6.04M

IBM puts AI-enabled attacks above one in four malicious breaches, averaging $6.04 million. The growth rate, not the average, is what should change remediation schedules.

Publishers:dev.to

Reality

Evidence34
Adoption48
Hype gap+12
Incentives72
Confidence38
productOne report1 publisher

MinIO went dark on 13 February. Docker will keep patching it until 2031, for a fee.

Archiving a project with a billion Docker pulls turned an object store into an audit finding. Docker's extended support does not remove the migration, it moves the deadline out to 2031.

Publishers:docker.com

Reality

Evidence28
Adoption24
Hype gap+34
Incentives92
Confidence32
securityOne report1 publisher

Reading OIDC tokens out of runner memory: ChainDrop and the poisoned build

Unit 42 says a worm hidden in more than 400 npm packages read GitHub Actions runner memory for temporary OIDC tokens. An SBOM generated at the end of the build would not have seen any of it.

Reality

Evidence55
Adoption62
Hype gap+18
Incentives80
Confidence52
productOne report1 publisher

Before You Pick An Algorithm, Find The Cryptography: The Case For A CBOM Built In CI

A devops.com argument worth acting on: post-quantum work starts as a discovery problem, and the first shippable artifact is a cryptographic inventory collected from the pipeline.

Publishers:devops.com

Reality

Evidence32
Adoption
Not scored
Hype gap+18
Incentives34
Confidence38
securityOne report1 publisher

The AsyncAPI backdoor shipped with valid provenance, because the official pipeline built it

Attackers moved upstream into the project's own repositories and release workflows, so the attestations checked out. Publisher reputation no longer tells you a build is clean.

Reality

Evidence42
Adoption28
Hype gap+22
Incentives82
Confidence40
productOne report1 publisher

Docker pipes every agent policy decision into your SIEM, and the evidence burden lands on platform teams

Docker AI Governance now streams every agent policy decision into the SIEM security already runs, with a searchable copy in Docker Cloud. Enforcement was the easy half.

Publishers:docker.com

Reality

Evidence30
Adoption34
Hype gap+38
Incentives86
Confidence55
buildOne report1 publisher

Goish ports Go 1.25's runtime into no_std Rust to test what the concurrency model is worth alone

A one-person project translates Go's scheduler, channels, net/http and crypto/tls into Rust with no GC, no glibc and no Tokio, and stamps every function with its Go source line.

Publishers:dev.to

Reality

Evidence30
Adoption6
Hype gap+38
Incentives68
Confidence42