openSUSE-SU-2026:20628-1 Security update for container-suseconnect
Not scored
Published
Check this codebase for openSUSE-SU-2026:20628-1 and fix it if it is affected.
What it is: openSUSE-SU-2026:20628-1 is a vulnerability, published on 27 Apr 2026.
Exploitation: There is no known exploitation of openSUSE-SU-2026:20628-1 in the wild and no public exploit code.
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-20628-1/ (Markdown: https://insights.sbomify.com/openSUSE-SU-2026-20628-1/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is openSUSE-SU-2026:20628-1?
openSUSE-SU-2026:20628-1 is a vulnerability, published on 27 Apr 2026.
Official description
This update for container-suseconnect fixes the following issues:
Changes in container-suseconnect:
- switch to build with go 1.25
Which versions are affected by openSUSE-SU-2026:20628-1?
How do I fix openSUSE-SU-2026:20628-1?
No fix has been published for openSUSE-SU-2026:20628-1 yet. Limit exposure of the affected software until one is available.
Is openSUSE-SU-2026:20628-1 being exploited?
There is no known exploitation of openSUSE-SU-2026:20628-1 in the wild and no public exploit code.