# CVE-2025-1269: Open Redirect in HAVELSAN's Open Source Project Liman MYS

> Attackers can redirect users to malicious sites via open redirect in Liman MYS, potentially facilitating phishing or credential theft.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:C/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Feb 2025
- **Updated:** 6 Jun 2026
- **Also known as:** GHSA-jhqw-cq3q-2p2g

## What is CVE-2025-1269?

CVE-2025-1269 is a medium-severity vulnerability in HAVELSAN Liman MYS, published on 18 Feb 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

URL Redirection to Untrusted Site ('Open Redirect') vulnerability in HAVELSAN Liman MYS allows Cross-Site Flashing.

This issue affects Liman MYS: before 2.1.1 - 1010.

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

## Which versions are affected by CVE-2025-1269?


## How do I fix CVE-2025-1269?

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

## Is CVE-2025-1269 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-1269 and fix it if it is affected.

What it is: CVE-2025-1269 is a medium-severity vulnerability in HAVELSAN Liman MYS, published on 18 Feb 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-1269 in the wild and no public exploit code.

Affected product: HAVELSAN Liman MYS. 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-2025-1269/ (Markdown: https://insights.sbomify.com/CVE-2025-1269/index.md)
```

## Sources

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

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