Skip to content

chore(deps): update rust crate tokio to v1.43.1 [security] - #253

Merged
jmjoy merged 1 commit into
masterfrom
renovate/crate-tokio-vulnerability
Oct 23, 2026
Merged

jmjoy merged 1 commit into
masterfrom
renovate/crate-tokio-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Oct 23, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
tokio (source) dependencies patch 1.43.0 → 1.43.1

Tokio broadcast channel calls clone in parallel, but does not require Sync

GHSA-rr8g-9fpq-6wmg

More information

Details

The broadcast channel internally calls clone on the stored value when receiving it, and only requires T:Send. This means that using the broadcast channel with values that are Send but not Sync can trigger unsoundness if the clone implementation makes use of the value being !Sync.

Thank you to Austin Bonander for finding and reporting this issue.

Severity

  • CVSS Score: 2.7 / 10 (Low)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

tokio-rs/tokio (tokio)

v1.43.1

Compare Source


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 is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

@jmjoy
jmjoy merged commit 525f56b into master Oct 23, 2026
21 checks passed
@jmjoy
jmjoy deleted the renovate/crate-tokio-vulnerability branch October 23, 2026 04:33
brettmc added a commit to brettmc/phper that referenced this pull request Oct 23, 2026
A security fix only updated Cargo.lock, so phper-framework#253 moved tokio to 1.43.1
and left `tokio = "1.43.0"` in three manifests. When the requirement
is a plain version, Renovate matches an alert against it rather than
the lockfile (CurrentVersionMatcher in its
lib/util/package-rules/current-version.ts). The alert still matched,
and phper-framework#256 followed with 1.43.2. Each later tokio release would have
opened another.

Bump the requirement on security fixes instead. The manifest then
leaves the vulnerable range and the alert stops matching after one
PR. Other updates keep the lockfile-only strategy and the monthly
group.

This raises the tokio requirement of the published phper-test crate
to the fixed version.

Assisted-By: Claude Code
jmjoy pushed a commit that referenced this pull request Oct 23, 2026
A security fix only updated Cargo.lock, so #253 moved tokio to 1.43.1
and left `tokio = "1.43.0"` in three manifests. When the requirement
is a plain version, Renovate matches an alert against it rather than
the lockfile (CurrentVersionMatcher in its
lib/util/package-rules/current-version.ts). The alert still matched,
and #256 followed with 1.43.2. Each later tokio release would have
opened another.

Bump the requirement on security fixes instead. The manifest then
leaves the vulnerable range and the alert stops matching after one
PR. Other updates keep the lockfile-only strategy and the monthly
group.

This raises the tokio requirement of the published phper-test crate
to the fixed version.

Assisted-By: Claude Code
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant