CVE-2025-3277VulnerabilityPublished 13 May 2025Updated 11 Oct 2026

SUSE · security update for nodejs

Affects SUSESource GCVE Database

Mentioned vulnerabilities

CVE-2025-31498

Authoritative record:CVE-2025-3277· Medium 6.9

Not known to be exploited · CVSS 6.9 Medium · fixed in SUSE package updates : update SUSE when convenient.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 1.2% chance of exploitation in 30 days – higher than 69% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 10.2, 10.1, 10.0

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L

Exploitation evidence

Disclosed: evidence found.
CVE published 14 Apr 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade SUSE to 10.2, 10.1 or 10.0.

Affected software

Product	Affected	Fixed in
SUSE Product Security Team SUSE	Affected >=10.0 <10.1 >=10.0 <10.2 >=9.0 <10.0	Fixed in 10.1 10.2 10.0

AI-suggested

Red Hat has released an official security update that addresses these vulnerabilities. Users should apply the provided update for the nodejs:22 module on Red Hat Enterprise Linux 9 and 10 variants as detailed in the Red Hat advisory RHSA-2025:7433. No additional mitigation steps are required beyond applying this update.

Description

Red Hat has released an important security update for the nodejs:22 module addressing two vulnerabilities: a use-after-free in c-ares (CVE-2025-31498) and an integer overflow in SQLite (CVE-2025-3277). These vulnerabilities affect Node.js as packaged in Red Hat Enterprise Linux 9 and 10 variants. No known exploits are reported in the wild at this time. The update mitigates these issues and is recommended to be applied promptly.

Impact

The use-after-free vulnerability in c-ares could lead to memory corruption, potentially causing crashes or arbitrary code execution. The integer overflow in SQLite could also lead to memory corruption or data integrity issues. However, there are no known exploits in the wild currently. The vulnerabilities affect Node.js environments running on affected Red Hat Enterprise Linux versions, potentially impacting applications relying on these components.

CWE-122Heap-based Buffer Overflow (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #16
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
Pre-design: Use a language or compiler that performs automatic bounds checking.
Architecture and Design
Use an abstraction library to abstract away risky APIs. Not a complete solution.
Operation · Build and Compilation · Environment Hardening
Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index…
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
Attack patterns
Forced Integer Overflow (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-416Use After Free (opens in a new tab)
Variant weaknessLikelihood of exploit: HighCWE Top 25 (2025): #7
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Architecture and Design · Language Selection
Choose a language that provides automatic memory management.
Implementation · Attack Surface Reduction
When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
OWASP Cheat Sheets
XML Security (opens in a new tab)
Mass Assignment (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.1 (opens in a new tab)
V5.1.4 (opens in a new tab)
V5.1.3 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Oct 2026, 22:15 UTC

WeaknessesCWE-122, CWE-416

Technical details

References

Community reviews

Related threats