# CVE-2025-30093: Missing authorization in n/a

> Authenticated attackers can bypass authorization restrictions in HTCondor, potentially escalating privileges or accessing unauthorized resources.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Mar 2025
- **Updated:** 28 Mar 2025
- **Also known as:** DEBIAN-CVE-2025-30093, GHSA-v64g-gxm8-whwj, UBUNTU-CVE-2025-30093

## What is CVE-2025-30093?

CVE-2025-30093 is a high-severity missing authorization vulnerability in n/a, published on 27 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

HTCondor 23.0.x before 23.0.22, 23.10.x before 23.10.22, 24.0.x before 24.0.6, and 24.6.x before 24.6.1 allows authenticated attackers to bypass authorization restrictions.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Wisc Htcondor.

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

Upgrade to a fixed version.

## Is CVE-2025-30093 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-25311](https://insights.sbomify.com/CVE-2021-25311/): Path traversal in n/a (critical 9.9)
- [CVE-2021-45102](https://insights.sbomify.com/CVE-2021-45102/): Auth bypass in n/a (high 8.8)
- [CVE-2021-25312](https://insights.sbomify.com/CVE-2021-25312/): Auth bypass in n/a (high 8.8)
- [CVE-2014-8126](https://insights.sbomify.com/CVE-2014-8126/): Code injection in HTCondor (high 8.8)
- [CVE-2012-3490](https://insights.sbomify.com/CVE-2012-3490/): Privilege escalation in Condor (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-30093 is a high-severity missing authorization vulnerability in n/a, published on 27 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-30093 in the wild and no public exploit code.

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

## Sources

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

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