# CVE-2025-49186: No brute-force protection

> The software lacks brute-force protection, allowing attackers to guess credentials and potentially take over accounts.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2025
- **Updated:** 13 May 2026
- **Also known as:** GHSA-437x-5r3x-xhcf

## What is CVE-2025-49186?

CVE-2025-49186 is a medium-severity missing authorization vulnerability in SICK AG Baggage Analytics, published on 12 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it susceptible to brute-force attacks.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

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

It affects 6 products.


Products: Avaya Media Server, Sick Baggage Analytics, Sick Field Analytics, Sick Logistic Diagnostic Analytics, Sick Package Analytics, Sick Tire Analytics.

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

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

## Is CVE-2025-49186 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-49186 is a medium-severity missing authorization vulnerability in SICK AG Baggage Analytics, published on 12 Jun 2025. 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-2025-49186 in the wild and no public exploit code.

Affected product: SICK AG Baggage Analytics. 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-49186/ (Markdown: https://insights.sbomify.com/CVE-2025-49186/index.md)
```

## Sources

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

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