openSUSE-SU-2026:20205-1 Security update for rust1.93
Not scored
Published
Check this codebase for openSUSE-SU-2026:20205-1 and fix it if it is affected.
What it is: openSUSE-SU-2026:20205-1 is a vulnerability in rust1.93, published on 12 Feb 2026.
Exploitation: There is no known exploitation of openSUSE-SU-2026:20205-1 in the wild and no public exploit code.
Affected product: rust1.93. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/openSUSE-SU-2026-20205-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2026-20205-1/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is openSUSE-SU-2026:20205-1?
openSUSE-SU-2026:20205-1 is a vulnerability in rust1.93, published on 12 Feb 2026.
Official description
This update for rust1.93 fixes the following issues:
Rust is shipped in 1.93.0 version.
Please see https://github.com/rust-lang/rust/releases/tag/1.93.0 for changes.
Which versions are affected by openSUSE-SU-2026:20205-1?
Linux distribution packages (1)
rust1.93 openSUSE:Leap 16.0 | All versions | 1.93.0-160000.1.1 |
How do I fix openSUSE-SU-2026:20205-1?
Upgrade to a fixed version.
Is openSUSE-SU-2026:20205-1 being exploited?
There is no known exploitation of openSUSE-SU-2026:20205-1 in the wild and no public exploit code.