Skip to main content
VulnerabilityPublished

CVE-2025-57141: rsbi-os · Code Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 54% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  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), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

European organizations should immediately conduct an inventory to identify deployments of rsbi-os 4.7 and assess their exposure to the sqlite-jdbc component. Until official patches are released, organizations should consider the following specific measures: 1) Restrict network access to systems running rsbi-os 4.7 to trusted internal networks only, minimizing exposure to external attackers. 2) Employ application-layer firewalls or intrusion prevention systems (IPS) with custom rules to detect and block suspicious database queries or anomalous JDBC traffic patterns. 3) Implement strict input validation and sanitization on all inputs interacting with the SQLite database to reduce injection risks. 4) Monitor logs for unusual activity indicative of exploitation attempts, such as unexpected command executions or database errors. 5) Prepare for rapid deployment of patches once available by establishing a vulnerability management process focused on this component. 6) Consider isolating or sandboxing affected applications to limit the blast radius of a potential compromise. 7) Engage with vendors or maintainers of rsbi-os and sqlite-jdbc for updates and advisories. These targeted actions go beyond generic advice by focusing on network segmentation, monitoring, and proactive preparation specific to this vulnerability and its context.

Description

rsbi-os 4.7 is vulnerable to Remote Code Execution (RCE) in sqlite-jdbc.

References

Community reviews

Loading reviews…