Loading vulnerability…
GEOritm versions through 2.45.1 contain a missing-authentication vulnerability in a REST API object-group function. Manipulation of the objectId argument permits access to affected API functionality without authentication from a remote location.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This small repository contains an Apache-2.0 license, a Russian/English README describing CVE-2026-100903, and one executable Bash proof-of-concept, ritm_park_enum.sh. The script exploits missing authentication in GEO.RITM REST API object methods. It first POSTs an empty JSON body to objects/obj-import-ts to collect object IDs and import timestamps, then POSTs each chosen objectId to objects/obj-groups. It supports a five-ID demonstration mode, a configurable limited enumeration, caller-selected IDs, or a full-fleet collection, with a configurable delay and output directory. Embedded Python code serializes raw API responses and renders a tabular inventory using group-name heuristics to infer vehicle type, division, region, responsible driver, deleted status, and activity age. The default connection target is 213.171.46.81:443 and requests force Host: ritm.avgust.com; users may alter the TCP target but not this Host header without editing the script. The code restricts its own POST helper to the two read-only endpoints and contains no command-execution, persistence, destructive, or shell payload capability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.