# CVE-2026-33047: Combodo iTop: Object can be locked by a user without write permissions

> Attackers without write permissions can lock objects in Combodo iTop, disrupting data integrity and availability for IT service management users.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2026
- **Updated:** 21 Aug 2026
- **Also known as:** GHSA-3qpj-3fcg-f5jc

## What is CVE-2026-33047?

CVE-2026-33047 is a medium-severity missing authorization vulnerability in Combodo iTop, published on 21 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Combodo iTop is a web based IT service management tool. Prior to 3.2.3, an object can be locked by a user who is not assigned write permissions. This issue has been fixed in version 3.2.3.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-33047?


## How do I fix CVE-2026-33047?

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

## Is CVE-2026-33047 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33047 and fix it if it is affected.

What it is: CVE-2026-33047 is a medium-severity missing authorization vulnerability in Combodo iTop, published on 21 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-33047 in the wild and no public exploit code.

Affected product: Combodo iTop. 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-2026-33047/ (Markdown: https://insights.sbomify.com/CVE-2026-33047/index.md)
```

## Sources

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

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