Skip to main content
VulnerabilityPublished Updated

CVE-2026-100903: GEOritm · Missing Authentication

Affects GEOritmSource CVE Database V5

0
Compare

Public exploit available · CVSS 6.9 Medium · fixed in 2.46 : patch GEOritm as a priority.

Data as of 10 Nov 2026, 23:24 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.46
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Sep 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GEOritmAffected
  • =2.45.0
  • =2.45.1
Fixed in–

CPE configurations (1)

  • cpe:2.3:a:_:georitm:*:*:*:*:*:*:*:*

AI-suggested

The vendor has released an official fix in GEOritm version 2.46 and has already applied the fix to their hosted GEO.RITM server. Users of affected versions 2.45.0 and 2.45.1 should upgrade to version 2.46 to remediate this vulnerability. No additional mitigation steps are indicated by the vendor.

Description

CVE-2026-100903 is a medium severity vulnerability in ООО НПО Ритм GEOritm versions 2.45.0 and 2.45.1. It involves missing authentication in the REST API component at the /restapi/objects/obj-groups endpoint, allowing remote attackers to manipulate the objectId argument without authentication. The vendor has fixed the issue in version 2.46 and on their hosted GEO.RITM server. Users are advised to upgrade to version 2.46 to mitigate the vulnerability.

References

Community reviews

Loading reviews…