SUSE-SU-2025:4220-1 Security update for govulncheck-vulndb
Not scored
Published
Check this codebase for SUSE-SU-2025:4220-1 and fix it if it is affected.
What it is: SUSE-SU-2025:4220-1 is a vulnerability in govulncheck-vulndb, published on 25 Nov 2025.
Exploitation: There is no known exploitation of SUSE-SU-2025:4220-1 in the wild and no public exploit code.
Affected product: govulncheck-vulndb. 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/SUSE-SU-2025-4220-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2025-4220-1/index.md)
Update govulncheck-vulndb to the latest version to ensure accurate detection of known Go vulnerabilities.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- Available
What is SUSE-SU-2025:4220-1?
SUSE-SU-2025:4220-1 is a vulnerability in govulncheck-vulndb, published on 25 Nov 2025.
Official description
This update for govulncheck-vulndb fixes the following issues:
Update to version 0.0.20251120T220319 2025-11-20T22:03:19Z. (jsc#PED-11136):
- GO-2023-2331
- GO-2024-2587
- GO-2025-3770
- GO-2025-4007
- GO-2025-4134
- GO-2025-4135
Update to version 0.0.20251118T154415 2025-11-18T15:44:15Z. (jsc#PED-11136):
- GO-2025-4025
- GO-2025-4090
- GO-2025-4091
- GO-2025-4093
- GO-2025-4094
- GO-2025-4095
- GO-2025-4096
- GO-2025-4097
- GO-2025-4098
- GO-2025-4099
- GO-2025-4100
- GO-2025-4101
- GO-2025-4102
- GO-2025-4103
- GO-2025-4104
- GO-2025-4105
- GO-2025-4106
- GO-2025-4107
- GO-2025-4108
- GO-2025-4109
- GO-2025-4110
- GO-2025-4111
- GO-2025-4112
- GO-2025-4113
- GO-2025-4114
- GO-2025-4115
- GO-2025-4117
- GO-2025-4118
- GO-2025-4119
- GO-2025-4120
- GO-2025-4121
- GO-2025-4122
- GO-2025-4123
- GO-2025-4124
- GO-2025-4125
- GO-2025-4126
- GO-2025-4127
- GO-2025-4128
- GO-2025-4129
- GO-2025-4130
- GO-2025-4131
Update to version 0.0.20251113T211203 2025-11-13T21:12:03Z (jsc#PED-11136):
- GO-2025-4116
Which versions are affected by SUSE-SU-2025:4220-1?
Linux distribution packages (2)
govulncheck-vulndb SUSE:Linux Enterprise Module for Package Hub 15 SP6 | All versions | 0.0.20251120T220319-150000.1.122.1 |
govulncheck-vulndb openSUSE:Leap 15.6 | All versions | 0.0.20251120T220319-150000.1.122.1 |
How do I fix SUSE-SU-2025:4220-1?
Upgrade to a fixed version.
Is SUSE-SU-2025:4220-1 being exploited?
There is no known exploitation of SUSE-SU-2025:4220-1 in the wild and no public exploit code.