mruby - Debian Package Tracker

general

source: mruby (main)
version: 3.4.0-3
maintainer: Nobuhiro Iwamatsu (DMD)
uploaders: Akira Mitsui [DMD]
arch: any
std-ver: 4.7.2
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 2.1.2-3
oldstable: 3.1.0-3
stable: 3.3.0-1
testing: 3.4.0-2
unstable: 3.4.0-3

versioned links

2.1.2-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.1.0-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.3.0-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.4.0-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.4.0-3: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

libmruby-dev
mruby

action needed

The VCS repository is not up to date, push the missing commits. high

vcswatch reports that the current version of the package is not in its VCS.
Either you need to push your commits and/or your tags, or the information about the package's VCS are out of date. A common cause of the latter issue when using the Git VCS is not specifying the correct branch when the packaging is not in the default one (remote HEAD branch), which is usually "master" but can be modified in salsa.debian.org in the project's general settings with the "Default Branch" field). Alternatively the Vcs-Git field in debian/control can contain a "-b <branch-name>" suffix to indicate what branch is used for the Debian packaging.

Created: 2026-06-20 Last update: 2026-06-24 08:02

2 security issues in sid high

There are 2 open security issues in sid.

2 important issues:

CVE-2026-1979: A flaw has been found in mruby up to 3.4.0. This affects the function mrb_vm_exec of the file src/vm.c of the component JMPNOT-to-JMPIF Optimization. Executing a manipulation can lead to use after free. The attack needs to be launched locally. The exploit has been published and may be used. This patch is called e50f15c1c6e131fa7934355eb02b8173b13df415. It is advisable to implement a patch to correct this issue.
CVE-2025-13120: A vulnerability has been found in mruby up to 3.4.0. This vulnerability affects the function sort_cmp of the file src/array.c. Such manipulation leads to use after free. 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 eb398971bfb43c38db3e04528b68ac9a7ce509bc. It is advisable to implement a patch to correct this issue.

Created: 2025-11-14 Last update: 2026-06-20 07:31

2 security issues in forky high

There are 2 open security issues in forky.

2 important issues:

CVE-2026-1979: A flaw has been found in mruby up to 3.4.0. This affects the function mrb_vm_exec of the file src/vm.c of the component JMPNOT-to-JMPIF Optimization. Executing a manipulation can lead to use after free. The attack needs to be launched locally. The exploit has been published and may be used. This patch is called e50f15c1c6e131fa7934355eb02b8173b13df415. It is advisable to implement a patch to correct this issue.
CVE-2025-13120: A vulnerability has been found in mruby up to 3.4.0. This vulnerability affects the function sort_cmp of the file src/array.c. Such manipulation leads to use after free. 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 eb398971bfb43c38db3e04528b68ac9a7ce509bc. It is advisable to implement a patch to correct this issue.

Created: 2025-11-14 Last update: 2026-06-20 07:31

Does not build reproducibly during testing normal

A package building reproducibly enables third parties to verify that the source matches the distributed binaries. It has been identified that this source package produced different results, failed to build or had other issues in a test environment. Please read about how to improve the situation!

Created: 2025-11-15 Last update: 2026-06-24 11:30

lintian reports 2 warnings normal

Lintian reports 2 warnings about this package. You should make the package lintian clean getting rid of them.

Created: 2025-08-16 Last update: 2025-08-16 20:34

debian/patches: 6 patches to forward upstream low

Among the 6 debian patches available in version 3.4.0-3 of the package, we noticed the following issues:

6 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2026-06-20 12:00

3 low-priority security issues in trixie low

There are 3 open security issues in trixie.

3 issues left for the package maintainer to handle:

CVE-2025-7207: (needs triaging) 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 apply a patch to fix this issue.
CVE-2026-1979: (needs triaging) A flaw has been found in mruby up to 3.4.0. This affects the function mrb_vm_exec of the file src/vm.c of the component JMPNOT-to-JMPIF Optimization. Executing a manipulation can lead to use after free. The attack needs to be launched locally. The exploit has been published and may be used. This patch is called e50f15c1c6e131fa7934355eb02b8173b13df415. It is advisable to implement a patch to correct this issue.
CVE-2025-13120: (needs triaging) A vulnerability has been found in mruby up to 3.4.0. This vulnerability affects the function sort_cmp of the file src/array.c. Such manipulation leads to use after free. 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 eb398971bfb43c38db3e04528b68ac9a7ce509bc. It is advisable to implement a patch to correct this issue.

You can find information about how to handle these issues in the security team's documentation.

Created: 2025-07-09 Last update: 2026-06-20 07:31

3 low-priority security issues in bookworm low

There are 3 open security issues in bookworm.

3 issues left for the package maintainer to handle:

CVE-2025-7207: (needs triaging) 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 apply a patch to fix this issue.
CVE-2026-1979: (needs triaging) A flaw has been found in mruby up to 3.4.0. This affects the function mrb_vm_exec of the file src/vm.c of the component JMPNOT-to-JMPIF Optimization. Executing a manipulation can lead to use after free. The attack needs to be launched locally. The exploit has been published and may be used. This patch is called e50f15c1c6e131fa7934355eb02b8173b13df415. It is advisable to implement a patch to correct this issue.
CVE-2025-13120: (needs triaging) A vulnerability has been found in mruby up to 3.4.0. This vulnerability affects the function sort_cmp of the file src/array.c. Such manipulation leads to use after free. 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 eb398971bfb43c38db3e04528b68ac9a7ce509bc. It is advisable to implement a patch to correct this issue.

You can find information about how to handle these issues in the security team's documentation.

Created: 2025-07-09 Last update: 2026-06-20 07:31

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.4 instead of 4.7.2).

Created: 2025-12-23 Last update: 2026-06-20 07:32

testing migrations

excuses:
- Migration status for mruby (3.4.0-2 to 3.4.0-3): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- ∙ ∙ Too young, only 4 of 5 days old
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/m/mruby.html
- ∙ ∙ Reproduced on amd64 - info
- ∙ ∙ Reproduced on arm64 - info
- ∙ ∙ Reproduced on armhf - info
- ∙ ∙ Reproduced on i386 - info
- Not considered

news

[rss feed]

[2026-06-19] Accepted mruby 3.4.0-3 (source) into unstable (Nobuhiro Iwamatsu)
[2025-08-21] mruby 3.4.0-2 MIGRATED to testing (Debian testing watch)
[2025-08-16] Accepted mruby 3.4.0-2 (source) into unstable (Nobuhiro Iwamatsu)
[2025-08-15] Accepted mruby 3.4.0-1 (source) into unstable (Nobuhiro Iwamatsu)
[2025-08-15] Accepted mruby 3.4.0-1~exp2 (source) into experimental (Nobuhiro Iwamatsu)
[2025-07-11] Accepted mruby 3.4.0-1~exp1 (source) into experimental (Nobuhiro Iwamatsu)
[2024-04-08] mruby 3.3.0-1 MIGRATED to testing (Debian testing watch)
[2024-04-03] Accepted mruby 3.3.0-1 (source) into unstable (Nobuhiro Iwamatsu)
[2024-02-07] Accepted mruby 3.3.0~rc2-1 (source) into experimental (Nobuhiro Iwamatsu)
[2023-09-11] mruby 3.2.0-2 MIGRATED to testing (Debian testing watch)
[2023-09-06] Accepted mruby 3.2.0-2 (source) into unstable (Nobuhiro Iwamatsu)
[2023-06-30] mruby 3.2.0-1 MIGRATED to testing (Debian testing watch)
[2023-06-25] Accepted mruby 3.2.0-1 (source) into unstable (Nobuhiro Iwamatsu)
[2023-04-17] mruby 3.1.0-3 MIGRATED to testing (Debian testing watch)
[2023-03-13] Accepted mruby 3.1.0-3 (source) into unstable (Nobuhiro Iwamatsu)
[2023-02-11] mruby 3.1.0-1 MIGRATED to testing (Debian testing watch)
[2023-02-11] Accepted mruby 3.1.0-2 (source) into experimental (Nobuhiro Iwamatsu)
[2022-12-14] Accepted mruby 3.1.0-1 (source) into unstable (Nobuhiro Iwamatsu)
[2022-08-30] mruby REMOVED from testing (Debian testing watch)
[2022-05-14] mruby 3.0.0-4 MIGRATED to testing (Debian testing watch)
[2022-05-09] Accepted mruby 3.0.0-4 (source amd64) into unstable (Nobuhiro Iwamatsu)
[2022-05-06] Accepted mruby 1.2.0+20161228+git30d5424a-1+deb9u1 (source amd64) into oldoldstable (Abhijith PA)
[2022-01-11] mruby 3.0.0-3 MIGRATED to testing (Debian testing watch)
[2022-01-06] Accepted mruby 3.0.0-3 (source) into unstable (Nobuhiro Iwamatsu)
[2022-01-06] Accepted mruby 3.0.0-2 (source) into unstable (Nobuhiro Iwamatsu)
[2021-09-28] mruby 3.0.0-1 MIGRATED to testing (Debian testing watch)
[2021-09-22] Accepted mruby 3.0.0-1 (source) into unstable (Nobuhiro Iwamatsu)
[2021-07-18] mruby 2.1.2-3 MIGRATED to testing (Debian testing watch)
[2021-07-13] Accepted mruby 2.1.2-3 (source) into unstable (Nobuhiro Iwamatsu)
[2021-01-01] mruby 2.1.2-2 MIGRATED to testing (Debian testing watch)

bugs [bug history graph]

all: 2
RC: 0
I&N: 2
M&W: 0
F&P: 0
patch: 0

links

homepage
lintian (0, 2)
buildd: logs, reproducibility, cross
popcon
browse source code
other distros
security tracker
screenshots
debian patches

ubuntu

[Information about Ubuntu for Debian Developers]

version: 3.4.0-3