# CVE-2019-25544: Pidgin 2.13.0 Denial of Service via Malformed Username

> Local attackers can crash Pidgin by entering an excessively long username during account creation, causing application unavailability.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Mar 2026
- **Updated:** 24 Mar 2026
- **Also known as:** GHSA-hvgh-8gm9-9vq2, SUSE-SU-2026:2967-1, UBUNTU-CVE-2019-25544

## What is CVE-2019-25544?

CVE-2019-25544 is a medium-severity denial of service vulnerability in Pidgin Pidgin, published on 21 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Pidgin 2.13.0 contains a denial of service vulnerability that allows local attackers to crash the application by providing an excessively long username string during account creation. Attackers can input a buffer of 1000 characters in the username field and trigger a crash when joining a chat, causing the application to become unavailable.

Weakness: CWE-807 (Reliance on Untrusted Inputs in a Security Decision)

## Which versions are affected by CVE-2019-25544?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `farstream` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 0.2.8-5.2.4 |
| `gssdp` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 0.14.16-7.2.1 |
| `gupnp` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 0.20.18-8.5.2 |
| `gupnp-igd` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 0.2.4-6.2.2 |
| `libgnt` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 2.14.3-4.3.8 |
| `libnice` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 0.1.13-7.2.3 |
| `pidgin` | SUSE:Linux Enterprise Server 12 SP5-LTSS | All versions | 2.14.8-3.9.3 |
| `farstream` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 0.2.8-5.2.4 |
| `gssdp` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 0.14.16-7.2.1 |
| `gupnp` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 0.20.18-8.5.2 |
| `gupnp-igd` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 0.2.4-6.2.2 |
| `libgnt` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 2.14.3-4.3.8 |
| `libnice` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 0.1.13-7.2.3 |
| `pidgin` | SUSE:Linux Enterprise Server LTSS Extended Security 12 SP5 | All versions | 2.14.8-3.9.3 |

Products: Pidgin Pidgin.

## How do I fix CVE-2019-25544?

Apply the vendor's patch.

## Is CVE-2019-25544 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25544 exists.

## Other vulnerabilities in Pidgin Pidgin

- [CVE-2013-6490](https://insights.sbomify.com/CVE-2013-6490/): Memory corruption in n/a (critical 10.0)
- [CVE-2016-1000030](https://insights.sbomify.com/CVE-2016-1000030/): Code injection in n/a (critical 9.8)
- [CVE-2013-6486](https://insights.sbomify.com/CVE-2013-6486/): Command injection in n/a (critical 9.3)
- [CVE-2011-3185](https://insights.sbomify.com/CVE-2011-3185/): Command injection in n/a (critical 9.3)
- [CVE-2009-1376](https://insights.sbomify.com/CVE-2009-1376/): Integer overflow in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25544 and fix it if it is affected.

What it is: CVE-2019-25544 is a medium-severity denial of service vulnerability in Pidgin Pidgin, published on 21 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-25544 exists.

Affected product: Pidgin Pidgin. 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-2019-25544/ (Markdown: https://insights.sbomify.com/CVE-2019-25544/index.md)
```

## Sources

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

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