Beyond the News
Sign in
Web DevelopmentDeveloper Tools Active dossier

Homebrew 7.0 turns package vulnerability checks into a built-in workflow — after closing a sudo-capable cask flaw

Homebrew 7.0 adds a native vulnerability scanner and Homebrew-specific OSV advisory database, tightens package-install sandboxing and provenance checks, and completes a security release cycle that included a high-severity flaw where unsigned cask-removal metadata could reach attacker-chosen commands through `sudo`.

Reviewed and published by Lars Jansen Updated 6 min read
Comment
First published

Key details

  1. Homebrew 7.0.0 was released September 13, 2026.
  2. `brew vulns` is now built in and can filter by severity, dependencies and whether a fix is available.
  3. Homebrew publishes its advisory records in OSV format and accounts for formula revisions/backported fixes.
  4. Homebrew 7.0's security notes list eight advisories across the 6.0.x-to-7.0 cycle.
  5. GHSA-rg9r-ppxp-87hm is High severity and was fixed in Homebrew 6.0.12.
  6. That flaw involved unsigned cask-removal metadata and could reach attacker-chosen commands through `sudo` under documented preconditions.
  7. A separate moderate LaunchServices sandbox escape was fixed in 7.0.0.
  8. Homebrew is moving package installation toward a networked fetch phase followed by a network-disabled install phase.
  9. Intel Macs and macOS Sonoma 14 are now Tier 3; routine Intel bottles have ended.
  10. Homebrew's Ubuntu 22.04 image is removed and Homebrew Actions should be pinned to releases or full SHAs.

What builders should take away

  1. Run `brew vulns` on developer and CI machines rather than assuming upstream version scanners understand Homebrew's patched revisions.
  2. Update Homebrew even if you are not ready to adopt every 7.0 workflow change; several security fixes landed in late 6.0.x releases before the major version.
  3. Treat package-manager API metadata and uninstall hooks as security-sensitive input, especially when privileged cleanup is possible.
  4. Audit CI references to Homebrew actions and images; `@master`, the old Ubuntu 22.04 image and unpinned moving branches now have migration consequences.
  5. If your team still develops on Intel Macs or Sonoma 14, plan for more source builds or migration rather than assuming the previous bottle/support model continues.
  6. On Linux, check `brew doctor`/Landlock support if you depend on Homebrew's sandbox as part of your build-security assumptions.

What changed

Homebrew released 7.0.0 on September 13, 2026 with a new built-in `brew vulns` command, a Homebrew-specific advisory database published in OSV format, stronger formula/cask sandboxing and expanded provenance checks. The release also closes the remaining moderate LaunchServices sandbox escape fixed specifically in 7.0.0 and summarizes seven other advisories fixed during the 6.0.x cycle. The most serious was GHSA-rg9r-ppxp-87hm, fixed in 6.0.12: Homebrew says unsigned cask-removal metadata could reach attacker-chosen commands through `sudo` when an attacker could tamper with the Homebrew API response and the installed cask needed artifact recovery. Homebrew deleted the vulnerable recovery path and related API accessors.

Why it matters

Homebrew sits in the development bootstrap path for a large amount of macOS and Linux software, so its security model affects far more than the `brew` binary itself. The new vulnerability workflow lets teams distinguish an upstream CVE from a Homebrew formula that has already backported the fix, reducing both blind spots and false alarms. At the same time, the recent advisories show that trusted package metadata, uninstall logic, Git configuration and sandbox escape paths can become privilege or supply-chain boundaries. The release also changes operational assumptions for Intel Macs, older macOS versions, CI images and third-party Homebrew actions.

`brew vulns` makes Homebrew-specific vulnerability state queryable

Homebrew 7.0 can scan installed formulae against known vulnerabilities using OSV.dev and Homebrew's own advisory data. The command supports severity filtering, dependency scans and fix-availability views. Homebrew's database records the formula versions and revisions it actually ships, including backported patches, so security teams can avoid flagging an upstream version string when Homebrew has already applied the fix.

A cask metadata path could escalate into sudo command execution

Homebrew's high-severity GHSA-rg9r-ppxp-87hm affected 6.0.11 and was fixed in 6.0.12. The advisory says artifact recovery for installed casks could read unsigned `cask/<token>.json` metadata and, under specific preconditions, use attacker-controlled uninstall arguments with an existing executable such as `/bin/sh` through a sudo path. Exploitation required an attacker able to control or tamper with Homebrew API responses plus a cask whose receipt lacked the needed uninstall metadata.

7.0 tightens the installation boundary beyond individual fixes

Formula and cask setup increasingly arrives as signed structured data. Homebrew is moving downloads into a network-enabled fetch phase followed by an install phase with networking disabled and caches read-only, and sandboxed builds can no longer read the user's home directory by default. On Linux, Landlock replaces Bubblewrap; kernels without sufficient Landlock support continue with weaker isolation and a `brew doctor` warning.

The release changes platform and CI support assumptions

Intel macOS is now Tier 3 with no routine new bottles, macOS Sonoma 14 is Tier 3, Catalina and earlier are unsupported, and the old Ubuntu 22.04 Homebrew image has been removed. Homebrew also wants GitHub Actions users to pin versioned actions or full SHAs rather than `@main` or the removed `@master` branch.

What to watch next

  • Whether `brew vulns` becomes a common CI or SBOM input and how quickly third-party security tools consume Homebrew's OSV data.
  • Further migration of formulae to the split fetch/install model with networking disabled during installation.
  • Whether Homebrew tightens behavior on Linux kernels that lack usable Landlock support.
  • How quickly Intel users experience missing bottles as formulae update.
  • Additional audits of cask uninstall/recovery metadata and package-manager privilege boundaries.

Still unclear

  • The high-severity cask issue required specific preconditions, including the ability to tamper with Homebrew API responses; the advisory does not establish widespread exploitation.
  • Seven of the eight advisories summarized by Homebrew 7.0 were already fixed in 6.0.x, so installing 7.0 is not the only way users received those fixes.
  • Homebrew's sandbox reduces package-install risk but Homebrew explicitly warns that it cannot make untrusted casks or vendor installers safe to execute.
  • Intel and older-macOS support may degrade unevenly because existing bottles remain while updated formulae may require local builds.

Sources

Direct reading behind this dossier.

2 sources
Homebrew 7.0.0
Homebrew primary release notes

Primary source for `brew vulns`, the advisory database, eight security advisories, sandbox changes, support migrations and CI changes.

Discussion

Discussion is reader-contributed. Comments are not part of the BTN dossier or its editorial evidence.

0 visible comments

Join the discussion

Keep comments useful and relevant. Reader contributions may be moderated and are not BTN editorial evidence.

Sign in to comment
Continue reading
Artificial Intelligence

GitHub AI Scan no longer needs CodeQL default setup

The scanner itself is not the new part. The September 16 change removes the CodeQL-default-setup gate that GitHub’s July rollout originally required, making AI-assisted vulnerability detection easier to add to repositories with different code-scanning configurations.