# CVE-2026-100903: ООО НПО Ритм GEOritm REST API obj-groups missing authentication

> Remote attackers can access or modify object groups without authentication due to missing checks in the REST API.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-g456-7977-c699

## What is CVE-2026-100903?

CVE-2026-100903 is a medium-severity missing authorization vulnerability in ООО НПО Ритм GEOritm, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was identified in ООО НПО Ритм GEOritm up to 2.45.1. This affects an unknown part of the file /restapi/objects/obj-groups of the component REST API. Such manipulation of the argument objectId leads to missing authentication. The attack can be launched remotely. The exploit is publicly available and might be used. Upgrading to version 2.46 is able to mitigate this issue. It is advisable to upgrade the affected component. The vendor confirms: "In August 2026, NPO Ritm received an official vulnerability notification from the Russian Federal Service for Technical and Export Control (FSTEC Russia). The vulnerability was registered under identifier BDU:2026-11235. Following our internal investigation, we confirmed the vulnerability and implemented the necessary security fixes. The vulnerability has been fixed on our hosted GEO.RITM server at geo.ritm.ru. The fix has also been included in GEO.RITM version 2.46, which is already being distributed to our customers."

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

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


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

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

## Is CVE-2026-100903 being exploited?

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

Public exploit code:

- GEOritm CVE (github_poc): https://github.com/4ybrick/CVE-2026-100903

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100903 is a medium-severity missing authorization vulnerability in ООО НПО Ритм GEOritm, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100903 exists.

Affected product: ООО НПО Ритм GEOritm. 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-100903/ (Markdown: https://insights.sbomify.com/CVE-2026-100903/index.md)
```

## Sources

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

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