# SUSE-SU-2026:3843-1: Security update for suseconnect-ng

> Update suseconnect-ng to fix flag parsing errors and improve registration handling, ensuring correct behavior for system registration and package management.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Aug 2026

## What is SUSE-SU-2026:3843-1?

SUSE-SU-2026:3843-1 is a vulnerability in suseconnect-ng, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This update for suseconnect-ng fixes the following issue:

- Update version to 1.23.0:
 
  - Use product identifier for product migrations. (bsc#1268596)
  - Switch to using go1.26-openssl as the default Go version to 
    install to support building the package (jsc#SCC-843, bsc#1268900).
  - Fix flag parsing so that unknown flags or options are flagged as an 
    error and the usage message is displayed. (bsc#1159776)
  - InstallReleasePackage interactive/noninteractive handling should 
    be consistent with DistUpgrade (bsc#1267478).
  - Add new optional rpm_packages collector, disabled by default, to 
    collect list of installed SUSE vendored RPM packages. (jsc#TEL-298)
  - Allow deregsiter when subscribed regcode has expired (bsc#1270392, 
    jsc#865)

## Which versions are affected by SUSE-SU-2026:3843-1?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `suseconnect-ng` | SUSE:Linux Enterprise Micro 5.3 | All versions | 1.23.0-150400.3.55.1 |
| `suseconnect-ng` | SUSE:Linux Enterprise Micro 5.4 | All versions | 1.23.0-150400.3.55.1 |

## How do I fix SUSE-SU-2026:3843-1?

Upgrade to a fixed version.

## Is SUSE-SU-2026:3843-1 being exploited?

There is no known exploitation of SUSE-SU-2026:3843-1 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for SUSE-SU-2026:3843-1 and fix it if it is affected.

What it is: SUSE-SU-2026:3843-1 is a vulnerability in suseconnect-ng, published on 27 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of SUSE-SU-2026:3843-1 in the wild and no public exploit code.

Affected product: suseconnect-ng. 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-2026-3843-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2026-3843-1/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/SUSE-SU-2026:3843-1

---
From sbomify Insights: https://insights.sbomify.com/SUSE-SU-2026-3843-1/
Summaries are generated and may contain mistakes; the official description above is the record.