CVE-2025-7207: A vulnerability, which was classified as problematic, was found in mruby up to 3.4.0-rc2

Q: How do I fix CVE-2025-7207?

mruby: upgrade to 3.4.0. Exact commands for each OS are on this page.

Q: Is CVE-2025-7207 being exploited?

CVE-2025-7207 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-7207 affect?

CVE-2025-7207 affects mruby. Severity is low (CVSS 3.3). A vulnerability, which was classified as problematic, was found in mruby up to 3.4.0-rc2. Affected is the function scope_new of the file mrbgems/mruby-compiler/core/codegen.c of the component nregs Handler. The manipulation leads to heap-ba

Q: How urgent is CVE-2025-7207?

Priority 21/100. Public exploit reference

Routine

LOW 3.3UPGRADE

CVE-2025-7207 is a low-severity flaw (CVSS 3.3) affecting mruby. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability, which was classified as problematic, was found in mruby up to 3.4.0-rc2. Affected is the function scope_new of the file mrbgems/mruby-compiler/core/codegen.c of the component nregs Handler. The manipulation leads to heap-based buffer overflow. An attack has to be approached locally. The exploit has been disclosed to the public and may be used. The name of the patch is 1fdd96104180cc0fb5d3cb086b05ab6458911bb9. It is recommended to

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	3.3 (Low)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 82%)
CISA exploited list	No
Weakness	CWE-119, CWE-122, CWE-787
Published	2025-07-09
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: mruby

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-07-09 01:15 UTCPublished CVE record published
2026-06-17 10:04 UTCUpdated Record last modified

mruby mruby UPGRADE

Affected: < 3.4.0 · 3.4.0 rc · 3.4.0 rc2

Fixed in: 3.4.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy mruby || rpm -q mruby || mruby --version

2. UPGRADE to 3.4.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade mruby

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade mruby

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-7207?

mruby: upgrade to 3.4.0. Exact commands for each OS are on this page.

Is CVE-2025-7207 being exploited?

CVE-2025-7207 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-7207 affect?

CVE-2025-7207 affects mruby. Severity is low (CVSS 3.3). A vulnerability, which was classified as problematic, was found in mruby up to 3.4.0-rc2. Affected is the function scope_new of the file mrbgems/mruby-compiler/core/codegen.c of the component nregs Handler. The manipulation leads to heap-ba

How urgent is CVE-2025-7207?

Priority 21/100. Public exploit reference

Related CVEs

CVE-2025-13120 MEDIUM 5.3 UPGRADE A vulnerability has been found in mruby up to 3.4.0
CVE-2025-12875 MEDIUM 5.3 DOWNGRADE A weakness has been identified in mruby 3.4.0
CVE-2026-1979 MEDIUM 5.3 UPGRADE A flaw has been found in mruby up to 3.4.0

References

← Back to latest CVEs