Update Rust crate tracing-subscriber to v0.3.23 - autoclosed #8

Closed
andras wants to merge 1 commit from renovate/tracing-subscriber-0.x-lockfile into main
Owner

This PR contains the following updates:

Package Type Update Change
tracing-subscriber (source) dependencies patch 0.3.19 → 0.3.23

Release Notes

tokio-rs/tracing (tracing-subscriber)

v0.3.23: tracing-subscriber 0.3.23

Compare Source

Fixed
  • Allow ansi sanitization to be disabled (#​3484)

v0.3.22: tracing-subscriber 0.3.22

Compare Source

Important

The previous release 0.3.21 was yanked as it depended explicitly on
tracing-0.1.42, which was yanked due to a breaking change (see #​3424 for
details). This release contains all the changes from the previous release, plus
an update to the newer version of tracing.

Changed

v0.3.21: tracing-subscriber 0.3.21

Compare Source

Fixed
  • Change registry exit to decrement local span ref only (#​3331)
  • Make Layered propagate on_register_dispatch (#​3379)
Changed
Performance
Documented
  • Fix a few small things in the format module (#​3339)
  • Fix extra closing brace in layer docs (#​3350)
  • Fix link in FmtSpan docs (#​3411)

v0.3.20: tracing-subscriber 0.3.20

Compare Source

Security Fix: ANSI Escape Sequence Injection (CVE-TBD)

Impact

Previous versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to:

  • Manipulate terminal title bars
  • Clear screens or modify terminal display
  • Potentially mislead users through terminal manipulation

In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator.

Solution

Version 0.3.20 fixes this vulnerability by escaping ANSI control characters in when writing events to destinations that may be printed to the terminal.

Affected Versions

All versions of tracing-subscriber prior to 0.3.20 are affected by this vulnerability.

Recommendations

Immediate Action Required: We recommend upgrading to tracing-subscriber 0.3.20 immediately, especially if your application:

  • Logs user-provided input (form data, HTTP headers, query parameters, etc.)
  • Runs in environments where terminal output is displayed to users

Migration

This is a patch release with no breaking API changes. Simply update your Cargo.toml:

[dependencies]
tracing-subscriber = "0.3.20"

Acknowledgments

We would like to thank zefr0x who responsibly reported the issue at security@tokio.rs.

If you believe you have found a security vulnerability in any tokio-rs project, please email us at security@tokio.rs.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

This PR contains the following updates: | Package | Type | Update | Change | |---|---|---|---| | [tracing-subscriber](https://tokio.rs) ([source](https://github.com/tokio-rs/tracing)) | dependencies | patch | `0.3.19` → `0.3.23` | --- ### Release Notes <details> <summary>tokio-rs/tracing (tracing-subscriber)</summary> ### [`v0.3.23`](https://github.com/tokio-rs/tracing/releases/tag/tracing-subscriber-0.3.23): tracing-subscriber 0.3.23 [Compare Source](https://github.com/tokio-rs/tracing/compare/tracing-subscriber-0.3.22...tracing-subscriber-0.3.23) ##### Fixed - Allow ansi sanitization to be disabled ([#&#8203;3484]) [#&#8203;3484]: https://github.com/tokio-rs/tracing/pull/3484 ### [`v0.3.22`](https://github.com/tokio-rs/tracing/releases/tag/tracing-subscriber-0.3.22): tracing-subscriber 0.3.22 [Compare Source](https://github.com/tokio-rs/tracing/compare/tracing-subscriber-0.3.21...tracing-subscriber-0.3.22) ##### Important The previous release [0.3.21] was yanked as it depended explicitly on [tracing-0.1.42], which was yanked due to a breaking change (see [#&#8203;3424] for details). This release contains all the changes from the previous release, plus an update to the newer version of `tracing`. ##### Changed - `tracing`: updated to 0.1.43 ([#&#8203;3427]) [#&#8203;3424]: https://github.com/tokio-rs/tracing/pull/3424 [#&#8203;3427]: https://github.com/tokio-rs/tracing/pull/3427 [0.3.21]: https://github.com/tokio-rs/tracing/releases/tag/tracing-subscriber-0.3.21 [tracing-0.1.42]: https://github.com/tokio-rs/tracing/releases/tag/tracing-0.1.42 ### [`v0.3.21`](https://github.com/tokio-rs/tracing/releases/tag/tracing-subscriber-0.3.21): tracing-subscriber 0.3.21 [Compare Source](https://github.com/tokio-rs/tracing/compare/tracing-subscriber-0.3.20...tracing-subscriber-0.3.21) ##### Fixed - Change registry exit to decrement local span ref only ([#&#8203;3331]) - Make Layered propagate `on_register_dispatch` ([#&#8203;3379]) ##### Changed - `tracing`: updated to 0.1.42 ([#&#8203;3418]) ##### Performance - Remove `clone_span` on enter ([#&#8203;3289]) ##### Documented - Fix a few small things in the format module ([#&#8203;3339]) - Fix extra closing brace in layer docs ([#&#8203;3350]) - Fix link in `FmtSpan` docs ([#&#8203;3411]) [#&#8203;3289]: https://github.com/tokio-rs/tracing/pull/#&#8203;3289 [#&#8203;3331]: https://github.com/tokio-rs/tracing/pull/#&#8203;3331 [#&#8203;3339]: https://github.com/tokio-rs/tracing/pull/#&#8203;3339 [#&#8203;3350]: https://github.com/tokio-rs/tracing/pull/#&#8203;3350 [#&#8203;3379]: https://github.com/tokio-rs/tracing/pull/#&#8203;3379 [#&#8203;3411]: https://github.com/tokio-rs/tracing/pull/#&#8203;3411 [#&#8203;3418]: https://github.com/tokio-rs/tracing/pull/#&#8203;3418 ### [`v0.3.20`](https://github.com/tokio-rs/tracing/releases/tag/tracing-subscriber-0.3.20): tracing-subscriber 0.3.20 [Compare Source](https://github.com/tokio-rs/tracing/compare/tracing-subscriber-0.3.19...tracing-subscriber-0.3.20) **Security Fix**: ANSI Escape Sequence Injection (CVE-TBD) #### Impact Previous versions of tracing-subscriber were vulnerable to ANSI escape sequence injection attacks. Untrusted user input containing ANSI escape sequences could be injected into terminal output when logged, potentially allowing attackers to: - Manipulate terminal title bars - Clear screens or modify terminal display - Potentially mislead users through terminal manipulation In isolation, impact is minimal, however security issues have been found in terminal emulators that enabled an attacker to use ANSI escape sequences via logs to exploit vulnerabilities in the terminal emulator. #### Solution Version 0.3.20 fixes this vulnerability by escaping ANSI control characters in when writing events to destinations that may be printed to the terminal. #### Affected Versions All versions of tracing-subscriber prior to 0.3.20 are affected by this vulnerability. #### Recommendations Immediate Action Required: We recommend upgrading to tracing-subscriber 0.3.20 immediately, especially if your application: - Logs user-provided input (form data, HTTP headers, query parameters, etc.) - Runs in environments where terminal output is displayed to users #### Migration This is a patch release with no breaking API changes. Simply update your Cargo.toml: ```toml [dependencies] tracing-subscriber = "0.3.20" ``` #### Acknowledgments We would like to thank [zefr0x](http://github.com/zefr0x) who responsibly reported the issue at `security@tokio.rs`. If you believe you have found a security vulnerability in any tokio-rs project, please email us at `security@tokio.rs`. </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xMDMuMiIsInVwZGF0ZWRJblZlciI6IjQ0LjExNi4xIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6W119-->
Update Rust crate tracing-subscriber to v0.3.23
All checks were successful
Build and Publish Docker Image / test (pull_request) Successful in 1m33s
Build and Publish Docker Image / build-and-push (pull_request) Successful in 1m5s
80f6b112b2
andras changed title from Update Rust crate tracing-subscriber to v0.3.23 to Update Rust crate tracing-subscriber to v0.3.23 - autoclosed 2026-10-29 00:17:11 +00:00
andras closed this pull request 2026-10-29 00:17:11 +00:00
All checks were successful
Build and Publish Docker Image / test (pull_request) Successful in 1m33s
Build and Publish Docker Image / build-and-push (pull_request) Successful in 1m5s

Pull request closed

Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
andras/docker-compose-updater!8
No description provided.