Skip to content

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Nov 20, 2025

Bumps the go_modules group with 4 updates in the / directory: github.com/cometbft/cometbft, github.com/hashicorp/go-getter, github.com/opencontainers/runc and github.com/ulikunitz/xz.

Updates github.com/cometbft/cometbft from 0.37.15 to 0.38.19

Release notes

Sourced from github.com/cometbft/cometbft's releases.

v0.38.19

This is a security patch release to the CometBFT v0.38.x family that fixes GHSA-hrhf-2vcr-ghch

What's Changed

Full Changelog: cometbft/cometbft@v0.38.18...v0.38.19

v0.38.18

What's Changed

Full Changelog: cometbft/cometbft@v0.38.17...v0.38.18

v0.38.17

See the CHANGELOG for this release.

... (truncated)

Changelog

Sourced from github.com/cometbft/cometbft's changelog.

v0.38.19

October 14, 2025

This release fixes two security issues, including (ASA-2025-003). Users are encouraged to upgrade as soon as possible.

Additionally included is a bug fix to properly prune extended commits (with vote extensions).

BUG-FIXES

  • [consensus] Reject oversized proposals (#5324)
  • [store] Prune extended commits properly (5275)
  • [bits] Validate BitArray mismatched Bits and Elems length (ASA-2025-003)

v0.38.18

July 3, 2025

Adds precommit metrics and reindex CLI command.

IMPROVEMENTS

  • Adds metrics that emit precommit data; precommit quorum delay from proposal, and precommit vote count and stake weight within timeout commit period. (#5251)

v0.38.17

February 3, 2025

This release fixes two security issues (ASA-2025-001, ASA-2025-002). Users are encouraged to upgrade as soon as possible.

BUG FIXES

  • [blocksync] Ban peer if it reports height lower than what was previously reported (ASA-2025-001)
  • [types] Check that Part.Index equals Part.Proof.Index (ASA-2025-001)

DEPENDENCIES

  • [go/runtime] Bump minimum Go version to 1.22.11 (#4891)

v0.38.16

... (truncated)

Commits

Updates github.com/hashicorp/go-getter from 1.7.8 to 1.7.9

Release notes

Sourced from github.com/hashicorp/go-getter's releases.

v1.7.9

What's Changed

New Contributors

Full Changelog: hashicorp/go-getter@v1.7.8...v1.7.9

Commits
  • e702211 Merge pull request #532 from hashicorp/dependabot/github_actions/actions-8948...
  • df0a14f [chore] : Bump the actions group with 8 updates
  • 87541b2 fix: go-getter subdir paths (#540)
  • 3713030 [Compliance] - PR Template Changes Required
  • af2dd3c Merge pull request #529 from hashicorp/dependabot-intge
  • bf52629 updating dependabot.yml
  • 1f63e10 changelog added, updated dependabot.yaml
  • 45af459 fix additional lint errors and increase linter scope
  • c8c6aba fix errcheck lint errors and run it as part of pr checks
  • 9b76f98 copywrite header added
  • Additional commits viewable in compare view

Updates github.com/opencontainers/runc from 1.3.0 to 1.3.3

Release notes

Sourced from github.com/opencontainers/runc's releases.

runc v1.3.3 -- "奴らに支配されていた恐怖を"

[!NOTE] Some vendors were given a pre-release version of this release. This public release includes two extra patches to fix regressions discovered very late during the embargo period and were thus not included in the pre-release versions. Please update to this version.

This release contains fixes for three high-severity security vulnerabilities in runc (CVE-2025-31133, CVE-2025-52565, and CVE-2025-52881). All three vulnerabilities ultimately allow (through different methods) for full container breakouts by bypassing runc's restrictions for writing to arbitrary /proc files.

Security

  • CVE-2025-31133 exploits an issue with how masked paths are implemented in runc. When masking files, runc will bind-mount the container's /dev/null inode on top of the file. However, if an attacker can replace /dev/null with a symlink to some other procfs file, runc will instead bind-mount the symlink target read-write. This issue affected all known runc versions.

  • CVE-2025-52565 is very similar in concept and application to CVE-2025-31133, except that it exploits a flaw in /dev/console bind-mounts. When creating the /dev/console bind-mount (to /dev/pts/$n), if an attacker replaces /dev/pts/$n with a symlink then runc will bind-mount the symlink target over /dev/console. This issue affected all versions of runc >= 1.0.0-rc3.

  • CVE-2025-52881 is a more sophisticated variant of CVE-2019-19921, which was a flaw that allowed an attacker to trick runc into writing the LSM process labels for a container process into a dummy tmpfs file and thus not apply the correct LSM labels to the container process. The mitigation we applied for CVE-2019-19921 was fairly limited and effectively only caused runc to verify that when we write LSM labels that those labels are actual procfs files. This issue affects all known runc versions.

Added

Static Linking Notices

The runc binary distributed with this release are statically linked with the following [GNU LGPL-2.1][lgpl-2.1] licensed libraries, with runc acting

... (truncated)

Changelog

Sourced from github.com/opencontainers/runc's changelog.

[1.3.3] - 2025-11-05

奴らに支配されていた恐怖を

Security

This release includes fixes for the following high-severity security issues:

  • CVE-2025-31133 exploits an issue with how masked paths are implemented in runc. When masking files, runc will bind-mount the container's /dev/null inode on top of the file. However, if an attacker can replace /dev/null with a symlink to some other procfs file, runc will instead bind-mount the symlink target read-write. This issue affected all known runc versions.

  • CVE-2025-52565 is very similar in concept and application to CVE-2025-31133, except that it exploits a flaw in /dev/console bind-mounts. When creating the /dev/console bind-mount (to /dev/pts/$n), if an attacker replaces /dev/pts/$n with a symlink then runc will bind-mount the symlink target over /dev/console. This issue affected all versions of runc >= 1.0.0-rc3.

  • CVE-2025-52881 is a more sophisticated variant of CVE-2019-19921, which was a flaw that allowed an attacker to trick runc into writing the LSM process labels for a container process into a dummy tmpfs file and thus not apply the correct LSM labels to the container process. The mitigation we applied for CVE-2019-19921 was fairly limited and effectively only caused runc to verify that when we write LSM labels that those labels are actual procfs files. This issue affects all known runc versions.

Added

[1.3.2] - 2025-10-02

Ночь, улица, фонарь, аптека...

Changed

  • The conversion from cgroup v1 CPU shares to cgroup v2 CPU weight is improved to better fit default v1 and v2 values. (#4772, #4785, #4897)
  • Dependency github.com/opencontainers/cgroups updated from v0.0.1 to v0.0.4. (#4897)

Fixed

... (truncated)

Commits
  • d842d77 VERSION: release v1.3.3
  • b370baf merge private security patches into ghsa-release-1.3.3
  • 4edba17 rootfs: re-allow dangling symlinks in mount targets
  • aca52c4 openat2: improve resilience on busy systems
  • 8b7e3d7 merge #4931 into opencontainers/runc:release-1.3
  • 2e82e55 tests: bfq: skip tests on misbehaving udev systems
  • f1627a7 tests: clean up loopback devices properly
  • 178e03c tests/int/update: fix getting block major
  • f14cad5 runc update: handle duplicated devs properly
  • 80da60e runc update: support per-device weight and iops
  • Additional commits viewable in compare view

Updates github.com/ulikunitz/xz from 0.5.12 to 0.5.14

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
    You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot dependabot bot added automerge dependencies Pull requests that update a dependency file labels Nov 20, 2025
@dependabot dependabot bot added dependencies Pull requests that update a dependency file automerge labels Nov 20, 2025
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Nov 20, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Comment @coderabbitai help to get the list of available commands and usage tips.

Bumps the go_modules group with 4 updates in the / directory: [github.com/cometbft/cometbft](https://github.com/cometbft/cometbft), [github.com/hashicorp/go-getter](https://github.com/hashicorp/go-getter), [github.com/opencontainers/runc](https://github.com/opencontainers/runc) and [github.com/ulikunitz/xz](https://github.com/ulikunitz/xz).


Updates `github.com/cometbft/cometbft` from 0.37.15 to 0.38.19
- [Release notes](https://github.com/cometbft/cometbft/releases)
- [Changelog](https://github.com/cometbft/cometbft/blob/v0.38.19/CHANGELOG.md)
- [Commits](cometbft/cometbft@v0.37.15...v0.38.19)

Updates `github.com/hashicorp/go-getter` from 1.7.8 to 1.7.9
- [Release notes](https://github.com/hashicorp/go-getter/releases)
- [Changelog](https://github.com/hashicorp/go-getter/blob/main/.goreleaser.yml)
- [Commits](hashicorp/go-getter@v1.7.8...v1.7.9)

Updates `github.com/opencontainers/runc` from 1.3.0 to 1.3.3
- [Release notes](https://github.com/opencontainers/runc/releases)
- [Changelog](https://github.com/opencontainers/runc/blob/v1.3.3/CHANGELOG.md)
- [Commits](opencontainers/runc@v1.3.0...v1.3.3)

Updates `github.com/ulikunitz/xz` from 0.5.12 to 0.5.14
- [Commits](ulikunitz/xz@v0.5.12...v0.5.14)

---
updated-dependencies:
- dependency-name: github.com/cometbft/cometbft
  dependency-version: 0.38.19
  dependency-type: direct:production
  dependency-group: go_modules
- dependency-name: github.com/hashicorp/go-getter
  dependency-version: 1.7.9
  dependency-type: indirect
  dependency-group: go_modules
- dependency-name: github.com/opencontainers/runc
  dependency-version: 1.3.3
  dependency-type: indirect
  dependency-group: go_modules
- dependency-name: github.com/ulikunitz/xz
  dependency-version: 0.5.14
  dependency-type: indirect
  dependency-group: go_modules
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/go_modules/go_modules-16b9fbe7ff branch from 32c839a to a581452 Compare December 18, 2025 16:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automerge dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants