# CVE-2026-14171: ads-tec Industrial IT: Post-login open redirect in the web interface

> An unauthenticated attacker can exploit improper post-login redirect validation to trick users into visiting malicious sites, compromising confidentiality and availability.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Jul 2026
- **Updated:** 28 Jul 2026
- **Also known as:** GHSA-83m8-9ppx-rj8m

## What is CVE-2026-14171?

CVE-2026-14171 is a medium-severity vulnerability in ads-tec Industrial IT DVG-IRF1401, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An unauthenticated remote attacker can abuse the improper validation of the post-login redirect  of the web-UI to trick users to a malicious website. This can result in a loss of confidentiality and availability.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2026-14171?


## How do I fix CVE-2026-14171?

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

## Is CVE-2026-14171 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-14171 and fix it if it is affected.

What it is: CVE-2026-14171 is a medium-severity vulnerability in ads-tec Industrial IT DVG-IRF1401, published on 28 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-14171 in the wild and no public exploit code.

Affected product: ads-tec Industrial IT DVG-IRF1401. 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-2026-14171/ (Markdown: https://insights.sbomify.com/CVE-2026-14171/index.md)
```

## Sources

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

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