- Details
EMERGENCY Security release!
Bug Fixes
- CVE-2025-27613, Gitk: When a user clones an untrusted repository and runs Gitk without additional command arguments, any writable file can be created and truncated. The option "Support per-file encoding" must have been enabled. The operation "Show origin of this line" is affected as well, regardless of the option being enabled or not.
- CVE-2025-27614, Gitk: A Git repository can be crafted in such a way that a user who has cloned the repository can be tricked into running any script supplied by the attacker by invoking
gitk filename, wherefilenamehas a particular structure. - CVE-2025-46334, Git GUI (Windows only): A malicious repository can ship versions of sh.exe or typical textconv filter programs such as astextplain. On Windows, path lookup can find such executables in the worktree. These programs are invoked when the user selects "Git Bash" or "Browse Files" from the menu.
- CVE-2025-46835, Git GUI: When a user clones an untrusted repository and is tricked into editing a file located in a maliciously named directory in the repository, then Git GUI can create and overwrite any writable file.
- CVE-2025-48384, Git: When reading a config value, Git strips any trailing carriage return and line feed (CRLF). When writing a config entry, values with a trailing CR are not quoted, causing the CR to be lost when the config is later read. When initializing a submodule, if the submodule path contains a trailing CR, the altered path is read resulting in the submodule being checked out to an incorrect location. If a symlink exists that points the altered path to the submodule hooks directory, and the submodule contains an executable post-checkout hook, the script may be unintentionally executed after checkout.
- CVE-2025-48385, Git: When cloning a repository Git knows to optionally fetch a bundle advertised by the remote server, which allows the server-side to offload parts of the clone to a CDN. The Git client does not perform sufficient validation of the advertised bundles, which allows the remote side to perform protocol injection. This protocol injection can cause the client to write the fetched bundle to a location controlled by the adversary. The fetched content is fully controlled by the server, which can in the worst case lead to arbitrary code execution.
- CVE-2025-48386, Git: The wincred credential helper uses a static buffer (
target) as a unique key for storing and comparing against internal storage. This credential helper does not properly bounds check the available space remaining in the buffer before appending to it withwcsncat(), leading to potential buffer overflows.
This release merges up the fixes that appear in v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, and v2.49.1 to address the following CVEs: CVE-2025-27613, CVE-2025-27614, CVE-2025-46334, CVE-2025-46835, CVE-2025-48384, CVE-2025-48385, and CVE-2025-48386. See the release notes for v2.43.7 for details.
- Details
17.5 - https://www.postgresql.org/docs/release/17.5/
16.9 - https://www.postgresql.org/docs/release/16.9/
15.13 - https://www.postgresql.org/docs/release/15.13/
14.18 - https://www.postgresql.org/docs/release/14.18/
13.21 - https://www.postgresql.org/docs/release/13.21/
- Details
- Fixed json schema issues with version validation (#12376)
- Fixed
bump-after-updatetriggering after anupdate --lock, which makes no sense (#12371) - Fixed zip bomb false positives when unpacking using
ZipArchive(#12409) - Fixed creation of empty archives (#12408)
- Removed output of script being run when running via
composer <script-name>(#12383)
- Details
All detailed changelogs are here
https://mariadb.com/docs/release-notes/mariadb-community-server-release-notes/changelogs
- Details
This release includes a fix for a YJIT bug related to local variables and addresses a build issue on Windows when using GCC 15. It was released ahead of schedule to make these fixes available as soon as possible. A few other bug fixes are also included.
Please see the release notes on GitHub for further details.
Release Schedule
We intend to release the latest stable Ruby version (currently Ruby 3.4) every two months following the most recent release. Following this release (3.4.4), Ruby 3.4.5 is scheduled for July, 3.4.6 for September, 3.4.7 for November, and 3.4.8 for January.
If a change arises that significantly affects users, a release may occur earlier than planned, and the subsequent schedule may shift accordingly.