# CVE-2025-14341: Input Data Manipulation in DivvyDrive Information Technologies' DivvyDrive

> Attackers can cause excessive resource allocation and flooding in DivvyDrive, leading to denial of service.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:H`)
- **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:** 7 May 2026
- **Updated:** 7 May 2026
- **Also known as:** GHSA-9439-7mjc-q3p7

## What is CVE-2025-14341?

CVE-2025-14341 is a high-severity denial of service vulnerability in DivvyDrive, published on 7 May 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

Improperly controlled modification of Dynamically-Determined object attributes, Allocation of resources without limits or throttling vulnerability in DivvyDrive Information Technologies Inc. DivvyDrive allows Excessive Allocation, Flooding.

This issue affects DivvyDrive: from 4.8.2.19 before 4.8.3.2.

Weakness: CWE-915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes), CWE-770 (Allocation of Resources Without Limits or Throttling)

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


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

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

## Is CVE-2025-14341 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14341 is a high-severity denial of service vulnerability in DivvyDrive, published on 7 May 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-2025-14341 in the wild and no public exploit code.

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

## Sources

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

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