CVE-2025-47907 | Incorrect results returned from Rows.Scan in database/sql

Cancelling a query (e.g. by cancelling the context passed to one of the query methods) during a call to the Scan method of the returned Rows can result in unexpected results if other queries are being made in parallel. This can result in a race condition that may overwrite the expected results with those of another query, causing the call to Scan to return either unexpected results from the other query or an error.

Published: 2025-08-07 Last update: 2026-01-29 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-47907 is rated Low Risk (36.9/100): CVSS High severity, with low exploitation likelihood (EPSS 0.33%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-47907

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.07% 0.33% +0.26%
2 2026-06-03 0.02% 0.07% +0.05%
3 2025-11-21 0.02%

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-47907

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.0 3.1 HIGH
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
2.2 4.7 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-47907

OS Trackers for CVE-2025-47907

vendor priority summary link
alpine CVE-2025-47907: 1 source package rows (go); 81 state rows across 2 repos (3.22-community, edge-community); fixed 2, open 79. https://security.alpinelinux.org/vuln/CVE-2025-47907
debian not yet assigned CVE-2025-47907 not yet assigned priority: Debian including 3 source packages (golang-1.15, golang-1.19, golang-1.24), 3 status rows across 3 suites (bookworm, bullseye, trixie): open 3. https://security-tracker.debian.org/tracker/CVE-2025-47907
redhat medium https://access.redhat.com/security/cve/CVE-2025-47907
suse medium CVE-2025-47907 severity moderate: SUSE including 87 source package names (azure-storage-azcopy-10.30.1-1.1, ca-certificates-mozilla-2.84-slfo.1.1_1.1, …), 416 product×package rows across 34 product lines (Container suse/sl-micro/6.0/baremetal-os-container, Container suse/sl-micro/6.0/base-os-container, … (34 product lines)): Fixed 375, Known Not Affected 41. https://www.suse.com/security/cve/CVE-2025-47907/
ubuntu medium CVE-2025-47907 medium priority: Ubuntu including 11 source packages (golang-1.10, golang-1.13, …), 70 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): needs-triage 40, DNE 28, ignored 2. https://ubuntu.com/security/CVE-2025-47907

Affected software / configurations for CVE-2025-47907

Vendor Product Version Raw CPE
golang go < 1.23.12 cpe:2.3:a:golang:go:*:*:*:*:*:*:*:*
golang go >= 1.24.0, < 1.24.6 cpe:2.3:a:golang:go:*:*:*:*:*:*:*:*

References for CVE-2025-47907

cvelogic Threat Intelligence