Fedora Security Advisories

• goose-1.45.0-2.el10_2

Update to goose-1.45.0-2.el10_2.

• goose-1.45.0-2.el10_4

Update to goose-1.45.0-2.el10_4.

• goose-1.45.0-2.el10_3

Update to goose-1.45.0-2.el10_3.

• goose-1.45.0-2.el9

Update to goose-1.45.0-2.el9.

• goose-1.45.0-2.fc43

Update to goose-1.45.0-2.fc43.

• goose-1.45.0-2.fc45

Update to goose-1.45.0-2.fc45.

• goose-1.45.0-2.fc44

Update to goose-1.45.0-2.fc44.

• composer-2.11.0-1.fc44

• Security: Fixed package names in vendor/composer/installed.json being able to escape the vendor directory during install and reinstall (GHSA-c968-33g3-wh7p)
• Security: Fixed inline repository HTTP headers, such as API tokens, being written into composer.lock (GHSA-fm2w-xgf2-f9fh)
• Security: Fixed additional arguments passed to @composer scripts not being escaped (#13169)
• Security: Fixed svn passwords not being redacted from debug output (#13171)
• Security: Sanitize URL-embedded credentials in hg and fossil error output (#13172)
• Improved dependency resolution performance and memory usage (#13174)
• Fixed config corrupting composer.json when modifying extra or scripts entries which are JSON arrays (#13167)
• Fixed archives not being unwrapped correctly when OS/editor metadata entries like __MACOSX or Thumbs.db sit next to the package's top-level dir (#13168)
• Fixed @script references with quoted arguments being split on spaces when passed to @composer scripts (#13169)

• composer-2.11.0-1.el10_4

• Security: Fixed package names in vendor/composer/installed.json being able to escape the vendor directory during install and reinstall (GHSA-c968-33g3-wh7p)
• Security: Fixed inline repository HTTP headers, such as API tokens, being written into composer.lock (GHSA-fm2w-xgf2-f9fh)
• Security: Fixed additional arguments passed to @composer scripts not being escaped (#13169)
• Security: Fixed svn passwords not being redacted from debug output (#13171)
• Security: Sanitize URL-embedded credentials in hg and fossil error output (#13172)
• Improved dependency resolution performance and memory usage (#13174)
• Fixed config corrupting composer.json when modifying extra or scripts entries which are JSON arrays (#13167)
• Fixed archives not being unwrapped correctly when OS/editor metadata entries like __MACOSX or Thumbs.db sit next to the package's top-level dir (#13168)
• Fixed @script references with quoted arguments being split on spaces when passed to @composer scripts (#13169)

• composer-2.11.0-1.el10_2

• Security: Fixed package names in vendor/composer/installed.json being able to escape the vendor directory during install and reinstall (GHSA-c968-33g3-wh7p)
• Security: Fixed inline repository HTTP headers, such as API tokens, being written into composer.lock (GHSA-fm2w-xgf2-f9fh)
• Security: Fixed additional arguments passed to @composer scripts not being escaped (#13169)
• Security: Fixed svn passwords not being redacted from debug output (#13171)
• Security: Sanitize URL-embedded credentials in hg and fossil error output (#13172)
• Improved dependency resolution performance and memory usage (#13174)
• Fixed config corrupting composer.json when modifying extra or scripts entries which are JSON arrays (#13167)
• Fixed archives not being unwrapped correctly when OS/editor metadata entries like __MACOSX or Thumbs.db sit next to the package's top-level dir (#13168)
• Fixed @script references with quoted arguments being split on spaces when passed to @composer scripts (#13169)

• composer-2.11.0-1.fc43

• Security: Fixed package names in vendor/composer/installed.json being able to escape the vendor directory during install and reinstall (GHSA-c968-33g3-wh7p)
• Security: Fixed inline repository HTTP headers, such as API tokens, being written into composer.lock (GHSA-fm2w-xgf2-f9fh)
• Security: Fixed additional arguments passed to @composer scripts not being escaped (#13169)
• Security: Fixed svn passwords not being redacted from debug output (#13171)
• Security: Sanitize URL-embedded credentials in hg and fossil error output (#13172)
• Improved dependency resolution performance and memory usage (#13174)
• Fixed config corrupting composer.json when modifying extra or scripts entries which are JSON arrays (#13167)
• Fixed archives not being unwrapped correctly when OS/editor metadata entries like __MACOSX or Thumbs.db sit next to the package's top-level dir (#13168)
• Fixed @script references with quoted arguments being split on spaces when passed to @composer scripts (#13169)

• composer-2.11.0-1.el9

• Security: Fixed package names in vendor/composer/installed.json being able to escape the vendor directory during install and reinstall (GHSA-c968-33g3-wh7p)
• Security: Fixed inline repository HTTP headers, such as API tokens, being written into composer.lock (GHSA-fm2w-xgf2-f9fh)
• Security: Fixed additional arguments passed to @composer scripts not being escaped (#13169)
• Security: Fixed svn passwords not being redacted from debug output (#13171)
• Security: Sanitize URL-embedded credentials in hg and fossil error output (#13172)
• Improved dependency resolution performance and memory usage (#13174)
• Fixed config corrupting composer.json when modifying extra or scripts entries which are JSON arrays (#13167)
• Fixed archives not being unwrapped correctly when OS/editor metadata entries like __MACOSX or Thumbs.db sit next to the package's top-level dir (#13168)
• Fixed @script references with quoted arguments being split on spaces when passed to @composer scripts (#13169)

• composer-2.11.0-1.el10_3

• Security: Fixed package names in vendor/composer/installed.json being able to escape the vendor directory during install and reinstall (GHSA-c968-33g3-wh7p)
• Security: Fixed inline repository HTTP headers, such as API tokens, being written into composer.lock (GHSA-fm2w-xgf2-f9fh)
• Security: Fixed additional arguments passed to @composer scripts not being escaped (#13169)
• Security: Fixed svn passwords not being redacted from debug output (#13171)
• Security: Sanitize URL-embedded credentials in hg and fossil error output (#13172)
• Improved dependency resolution performance and memory usage (#13174)
• Fixed config corrupting composer.json when modifying extra or scripts entries which are JSON arrays (#13167)
• Fixed archives not being unwrapped correctly when OS/editor metadata entries like __MACOSX or Thumbs.db sit next to the package's top-level dir (#13168)
• Fixed @script references with quoted arguments being split on spaces when passed to @composer scripts (#13169)

• composer-2.11.0-1.fc45

• Security: Fixed package names in vendor/composer/installed.json being able to escape the vendor directory during install and reinstall (GHSA-c968-33g3-wh7p)
• Security: Fixed inline repository HTTP headers, such as API tokens, being written into composer.lock (GHSA-fm2w-xgf2-f9fh)
• Security: Fixed additional arguments passed to @composer scripts not being escaped (#13169)
• Security: Fixed svn passwords not being redacted from debug output (#13171)
• Security: Sanitize URL-embedded credentials in hg and fossil error output (#13172)
• Improved dependency resolution performance and memory usage (#13174)
• Fixed config corrupting composer.json when modifying extra or scripts entries which are JSON arrays (#13167)
• Fixed archives not being unwrapped correctly when OS/editor metadata entries like __MACOSX or Thumbs.db sit next to the package's top-level dir (#13168)
• Fixed @script references with quoted arguments being split on spaces when passed to @composer scripts (#13169)

• python-pydantic-core-2.46.5-6.fc45

Update lru to 0.18.2 for RUSTSEC-2026-0253. Allow jiter 0.18.

• wordpress-7.1.4-1.fc45

Security updates included in this release

• A weakness in the WordPress upgrade process which can lead to remote code execution during the upgrade window, reported by Umut Bayram.
• A stored XSS with specially crafted block markup, reported by Rafie Muhammad (Awesome Motive, Inc.).
• Privacy Data Removal Requests can be created in a way that leads to stored XSS, reported by Anthropic.
• Multiple stored XSS issues in the Interactivity API independently discovered by AnC and DatNLQ from VietSunshine Cyber Security, rekter0 and Anas cherni, Marcel Karlsson (whoismarcel), and Weston Ruter, Jon Surrell, Alex Concha, and Luis Herranz of the WordPress Security Team.
• A stored denial of service issue in the Interactivity API, reported by Jon Surrell of the WordPress Security Team.
• A stored XSS in Customizer selective refresh, reported by Rafie Muhammad (Awesome Motive, Inc.).
• A Stored XSS in the Categories block reported by Ben Bidner of the WordPress Security Team.
• Specially crafted User Logins can lead to a stored XSS reported by Anthropic.
• Unpublished customizer changesets can be discovered by unauthenticated users, reported by Antonio Lorensius Silaban.
• A Stored XSS in Playlist and image blocks, reported by Ben Bidner of the WordPress Security Team. Stored XSS in core/comments-pagination-next and core/comments-pagination-previous blocks, reported by Alex Concha of the WordPress Security Team.
• Notes can be read by privileged users that lack access to edit the post the note is attached to, reported by Ramon of the WordPress Security Team. -An update to the bundled root certificates due to the eMudhra revocation.

• wordpress-6.9.11-1.el10_2

Security updates included in this release

• A weakness in the WordPress upgrade process which can lead to remote code execution during the upgrade window, reported by Umut Bayram.
• A stored XSS with specially crafted block markup, reported by Rafie Muhammad (Awesome Motive, Inc.).
• Privacy Data Removal Requests can be created in a way that leads to stored XSS, reported by Anthropic.
• Multiple stored XSS issues in the Interactivity API independently discovered by AnC and DatNLQ from VietSunshine Cyber Security, rekter0 and Anas cherni, Marcel Karlsson (whoismarcel), and Weston Ruter, Jon Surrell, Alex Concha, and Luis Herranz of the WordPress Security Team.
• A stored denial of service issue in the Interactivity API, reported by Jon Surrell of the WordPress Security Team.
• A stored XSS in Customizer selective refresh, reported by Rafie Muhammad (Awesome Motive, Inc.).
• A Stored XSS in the Categories block reported by Ben Bidner of the WordPress Security Team.
• Specially crafted User Logins can lead to a stored XSS reported by Anthropic.
• Unpublished customizer changesets can be discovered by unauthenticated users, reported by Antonio Lorensius Silaban.
• A Stored XSS in Playlist and image blocks, reported by Ben Bidner of the WordPress Security Team. Stored XSS in core/comments-pagination-next and core/comments-pagination-previous blocks, reported by Alex Concha of the WordPress Security Team.
• Notes can be read by privileged users that lack access to edit the post the note is attached to, reported by Ramon of the WordPress Security Team. -An update to the bundled root certificates due to the eMudhra revocation.

• wordpress-7.1.4-1.el10_3

Security updates included in this release

• A weakness in the WordPress upgrade process which can lead to remote code execution during the upgrade window, reported by Umut Bayram.
• A stored XSS with specially crafted block markup, reported by Rafie Muhammad (Awesome Motive, Inc.).
• Privacy Data Removal Requests can be created in a way that leads to stored XSS, reported by Anthropic.
• Multiple stored XSS issues in the Interactivity API independently discovered by AnC and DatNLQ from VietSunshine Cyber Security, rekter0 and Anas cherni, Marcel Karlsson (whoismarcel), and Weston Ruter, Jon Surrell, Alex Concha, and Luis Herranz of the WordPress Security Team.
• A stored denial of service issue in the Interactivity API, reported by Jon Surrell of the WordPress Security Team.
• A stored XSS in Customizer selective refresh, reported by Rafie Muhammad (Awesome Motive, Inc.).
• A Stored XSS in the Categories block reported by Ben Bidner of the WordPress Security Team.
• Specially crafted User Logins can lead to a stored XSS reported by Anthropic.
• Unpublished customizer changesets can be discovered by unauthenticated users, reported by Antonio Lorensius Silaban.
• A Stored XSS in Playlist and image blocks, reported by Ben Bidner of the WordPress Security Team. Stored XSS in core/comments-pagination-next and core/comments-pagination-previous blocks, reported by Alex Concha of the WordPress Security Team.
• Notes can be read by privileged users that lack access to edit the post the note is attached to, reported by Ramon of the WordPress Security Team. -An update to the bundled root certificates due to the eMudhra revocation.

• wordpress-6.9.11-1.fc44

Security updates included in this release

• A weakness in the WordPress upgrade process which can lead to remote code execution during the upgrade window, reported by Umut Bayram.
• A stored XSS with specially crafted block markup, reported by Rafie Muhammad (Awesome Motive, Inc.).
• Privacy Data Removal Requests can be created in a way that leads to stored XSS, reported by Anthropic.
• Multiple stored XSS issues in the Interactivity API independently discovered by AnC and DatNLQ from VietSunshine Cyber Security, rekter0 and Anas cherni, Marcel Karlsson (whoismarcel), and Weston Ruter, Jon Surrell, Alex Concha, and Luis Herranz of the WordPress Security Team.
• A stored denial of service issue in the Interactivity API, reported by Jon Surrell of the WordPress Security Team.
• A stored XSS in Customizer selective refresh, reported by Rafie Muhammad (Awesome Motive, Inc.).
• A Stored XSS in the Categories block reported by Ben Bidner of the WordPress Security Team.
• Specially crafted User Logins can lead to a stored XSS reported by Anthropic.
• Unpublished customizer changesets can be discovered by unauthenticated users, reported by Antonio Lorensius Silaban.
• A Stored XSS in Playlist and image blocks, reported by Ben Bidner of the WordPress Security Team. Stored XSS in core/comments-pagination-next and core/comments-pagination-previous blocks, reported by Alex Concha of the WordPress Security Team.
• Notes can be read by privileged users that lack access to edit the post the note is attached to, reported by Ramon of the WordPress Security Team. -An update to the bundled root certificates due to the eMudhra revocation.

• wordpress-6.9.11-1.fc43

Security updates included in this release

• A weakness in the WordPress upgrade process which can lead to remote code execution during the upgrade window, reported by Umut Bayram.
• A stored XSS with specially crafted block markup, reported by Rafie Muhammad (Awesome Motive, Inc.).
• Privacy Data Removal Requests can be created in a way that leads to stored XSS, reported by Anthropic.
• Multiple stored XSS issues in the Interactivity API independently discovered by AnC and DatNLQ from VietSunshine Cyber Security, rekter0 and Anas cherni, Marcel Karlsson (whoismarcel), and Weston Ruter, Jon Surrell, Alex Concha, and Luis Herranz of the WordPress Security Team.
• A stored denial of service issue in the Interactivity API, reported by Jon Surrell of the WordPress Security Team.
• A stored XSS in Customizer selective refresh, reported by Rafie Muhammad (Awesome Motive, Inc.).
• A Stored XSS in the Categories block reported by Ben Bidner of the WordPress Security Team.
• Specially crafted User Logins can lead to a stored XSS reported by Anthropic.
• Unpublished customizer changesets can be discovered by unauthenticated users, reported by Antonio Lorensius Silaban.
• A Stored XSS in Playlist and image blocks, reported by Ben Bidner of the WordPress Security Team. Stored XSS in core/comments-pagination-next and core/comments-pagination-previous blocks, reported by Alex Concha of the WordPress Security Team.
• Notes can be read by privileged users that lack access to edit the post the note is attached to, reported by Ramon of the WordPress Security Team. -An update to the bundled root certificates due to the eMudhra revocation.