# CVE-2026-34949: Combodo iTop: Unauthenticated user can delete .readonly file

> Unauthenticated attackers can delete the .readonly file, bypassing write restrictions and enabling unauthorized data modification in Combodo iTop.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-2xh3-r27f-3pr5

## What is CVE-2026-34949?

CVE-2026-34949 is a medium-severity missing authorization vulnerability in Combodo iTop, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Combodo iTop is a web based IT service management tool.Prior to 3.2.3, an unauthenticated user could delete the .readonly file on iTop instances — a file created during the setup process that prevents users from performing write actions. This issue has been fixed in version 3.2.3.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2026-34949 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34949 is a medium-severity missing authorization vulnerability in Combodo iTop, published on 21 Aug 2026. 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-2026-34949 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-34949/ (Markdown: https://insights.sbomify.com/CVE-2026-34949/index.md)
```

## Sources

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

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