CVE-2026-100903

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-09-28. A secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 5 sources updated this weekElevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 5.3Exploit: Elevated riskExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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."

CVSS v3
5.3
EG Score
5.3MEDIUMhigh confidence
EG Risk
55
EG Risk 55/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation40% × 40%
Automatability100% × 15%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.5%
EPSS %ILE
37th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 28, 2026

Last Modified

October 1, 2026

Advisory Details (2)

Auto-updated Sep 28, 2026
No patch confirmed yet.
generic

���������� ���������� - ��� ������

https://ritm.ru/contacts/
generic

#!/usr/bin/env bash## GEO.RITM REST API — CWE-306 Missing Authentication PoC - Pastebin.com

https://pastebin.com/3VsEG3Rg

Vendor Advisories for CVE-2026-100903(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 35× in last 7d / 35× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 09:40 UTCEG score recompute
  2. 2026-10-04 09:40 UTCGHSA enrichment
  3. 2026-10-03 14:25 UTCEPSS rescore
  4. 2026-10-03 11:41 UTCEG score recompute
  5. 2026-10-03 11:41 UTCGHSA enrichment
  6. 2026-10-02 13:21 UTCEG score recompute
  7. 2026-10-02 13:21 UTCGHSA enrichment
  8. 2026-10-01 19:49 UTCEPSS rescore
  9. 2026-10-01 15:25 UTCEG score recompute
  10. 2026-10-01 15:24 UTCGHSA enrichment
  11. 2026-10-01 15:22 UTCNVD updateCVSS v4 → 5.5
  12. 2026-10-01 14:22 UTCEG score recompute
  13. 2026-10-01 14:22 UTCGHSA enrichment
  14. 2026-10-01 14:20 UTCMITRE cvelistV5CVSS v4 → 6.9
  15. 2026-10-01 09:18 UTCEG score recompute
  16. 2026-10-01 09:18 UTCGHSA enrichment
  17. 2026-09-30 15:02 UTCEPSS rescore
  18. 2026-09-30 11:22 UTCEG score recompute
  19. 2026-09-30 11:22 UTCGHSA enrichment
  20. 2026-09-29 15:20 UTCEPSS rescore
  21. 2026-09-29 13:25 UTCEG score recompute
  22. 2026-09-29 13:25 UTCGHSA enrichment
  23. 2026-09-28 15:28 UTCEG score recompute
  24. 2026-09-28 15:28 UTCGHSA enrichment
  25. 2026-09-28 13:50 UTCEPSS rescore
Show 10 more
  1. 2026-09-28 12:31 UTCEG score recompute
  2. 2026-09-28 12:31 UTCGHSA enrichment
  3. 2026-09-28 12:30 UTCNVD updateCVSS v4 → 5.5
  4. 2026-09-28 11:47 UTCEG score recompute
  5. 2026-09-28 11:47 UTCGHSA enrichment
  6. 2026-09-28 11:46 UTCMITRE cvelistV5CVSS v4 → 6.9
  7. 2026-09-28 04:19 UTCEG score recompute
  8. 2026-09-28 04:19 UTCNVD updateCVSS v4 → 5.5
  9. 2026-09-28 03:27 UTCEG score recompute
  10. 2026-09-28 03:27 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-100903?
CVE-2026-100903 is a medium vulnerability published on September 28, 2026. 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…
When was CVE-2026-100903 disclosed?
CVE-2026-100903 was first published on September 28, 2026, with the most recent update on October 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-100903 actively exploited?
CVE-2026-100903 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-100903?
CVE-2026-100903 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-100903?
No fix for CVE-2026-100903 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-100903 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-100903

Explore →

Is Your Infrastructure Affected by CVE-2026-100903?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs