# CVE-2022-50981: Multiple Innomic VibroLine VLX HD 5.0 and avibia AVLX weak password requirements

> Unauthenticated attackers can gain full access to Innomic and avibia devices because they ship with no password and do not enforce password creation.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Feb 2026
- **Updated:** 2 Feb 2026
- **Also known as:** GHSA-47f4-2884-x6r8

## What is CVE-2022-50981?

CVE-2022-50981 is a critical vulnerability in Innomic AvibiaLine AVLE1 HD 5.0, published on 2 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unauthenticated remote attacker can gain full access on the affected devices as they are shipped without a password by default and setting one is not enforced.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2022-50981?


## How do I fix CVE-2022-50981?

No fix has been published for CVE-2022-50981 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-50981 being exploited?

There is no known exploitation of CVE-2022-50981 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50981 and fix it if it is affected.

What it is: CVE-2022-50981 is a critical vulnerability in Innomic AvibiaLine AVLE1 HD 5.0, published on 2 Feb 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 CVE-2022-50981 in the wild and no public exploit code.

Affected product: Innomic AvibiaLine AVLE1 HD 5.0. 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/CVE-2022-50981/ (Markdown: https://insights.sbomify.com/CVE-2022-50981/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-50981
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-50981
- OSV: https://osv.dev/vulnerability/CVE-2022-50981

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-50981/
Summaries are generated and may contain mistakes; the official description above is the record.