How severe is GHSA-3jmm-f6jj-rcc3?

GHSA-3jmm-f6jj-rcc3 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-3jmm-f6jj-rcc3?

GHSA-3jmm-f6jj-rcc3 affects the following packages: github.com/rudderlabs/rudder-server (Go). Ecosystems affected: Go.

How do I fix GHSA-3jmm-f6jj-rcc3?

Update github.com/rudderlabs/rudder-server to 1.3.0-rc.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3jmm-f6jj-rcc3 is resolved across your whole dependency graph.

How do I detect GHSA-3jmm-f6jj-rcc3 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/rudderlabs/rudder-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-3jmm-f6jj-rcc3 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is GHSA-3jmm-f6jj-rcc3 actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-3jmm-f6jj-rcc3, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-3jmm-f6jj-rcc3?

GHSA-3jmm-f6jj-rcc3 has an EPSS (Exploit Prediction Scoring System) score of 85.8%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is GHSA-3jmm-f6jj-rcc3?

GHSA-3jmm-f6jj-rcc3 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for GHSA-3jmm-f6jj-rcc3?

A Nuclei detection template exists for GHSA-3jmm-f6jj-rcc3, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-3jmm-f6jj-rcc3 published, and has it been updated?

GHSA-3jmm-f6jj-rcc3 was published on August 5, 2024 and was last updated on November 18, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

rudder-server is vulnerable to SQL injectionGHSA-3jmm-f6jj-rcc3

HIGHFix: rudderlabs/rudder-server#2652

GHSA-3jmm-f6jj-rcc3 is a high-severity (CVSS 8.8) SQL Injection vulnerability in github.com/rudderlabs/rudder-server. 2 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for github.com/rudderlabs/rudder-server — see the affected versions and patch details below.

Also known asCVE-2023-30625GO-2023-1863

Published

Aug 5, 2024

Updated

Nov 18, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

2 known

Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-3jmm-f6jj-rcc3.

EPSS Exploitation Probability

via FIRST.org ↗

85.8%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐹github.com/rudderlabs/rudder-server

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

rudder-server is part of RudderStack, an open source Customer Data Platform (CDP). Versions of rudder-server prior to 1.3.0-rc.1 are vulnerable to SQL injection. This issue may lead to Remote Code Execution (RCE) due to the rudder role in PostgresSQL having superuser permissions by default. Version 1.3.0-rc.1 contains patches for this issue.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/rudderlabs/rudder-server`	all versions	1.3.0-rc.1`go get github.com/rudderlabs/rudder-server@v1.3.0-rc.1`

Affected Products

1 product · 1 configurations

Application

rudder-serverrudderstack

≤ 1.2.5

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

rudder-server is part of RudderStack, an open source Customer Data Platf…

securitylab.github.comNVDJun 2023

Report on github.com

github.comMetasploitJul 2023

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/rudderlabs/rudder-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/rudderlabs/rudder-server to 1.3.0-rc.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3jmm-f6jj-rcc3 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

How to detect GHSA-3jmm-f6jj-rcc3

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id ghsa-3jmm-f6jj-rcc3 -u https://target

Template: Rudder Server < 1.3.0-rc.1 - SQL Injection
Severity: high
Impact: Authenticated attackers can execute arbitrary SQL commands and potentially achieve remote code execution due to PostgreSQL superuser permissions, leading to complete database and server compromise.
Remediation: Upgrade to Rudder Server version 1.3.0-rc.1 or later.

Template by ProjectDiscovery nuclei-templates (gy741), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

rudder-server is part of RudderStack, an open source Customer Data Platform (CDP). Versions of rudder-server prior to 1.3.0-rc.1 are vulnerable to SQL injection. This issue may lead to Remote Code Execution (RCE) due to the `rudder` role in PostgresSQL having superuser permissions by default. Version 1.3.0-rc.1 contains patches for this issue.

O3 Security · Impact-Aware SCA

Is GHSA-3jmm-f6jj-rcc3 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works