CVE-2025-3416VulnerabilityPublished 18 Aug 2026Updated 17 Sep 2026

SUSE forgejo-cli · Security update for forgejo-cli

Affects SUSE forgejo-cliSource GCVE Database

Compare

Mentioned vulnerabilities

CVE-2026-25541

Not known to be exploited.

Data as of 31 Oct 2026, 20:20 UTC

Severity

High

Rated by Threat Radar · CVSS not yet scored by NVD

EPSS: 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 31 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity 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

Affected software

Product	Affected	Fixed in
SUSEsuse/forgejo-cli`pkg:rpm/suse/forgejo-cli`Other threats	Affected =0.6.0-bp160.1.1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available by updating forgejo-cli to the version that includes the updated bytes crate 1.12.1. Users should apply this update to remediate the integer overflow vulnerability. No additional mitigation steps are indicated.

Description

A security update for forgejo-cli addresses an integer overflow vulnerability in the vendored bytes crate (CVE-2026-25541) that could corrupt tracked capacity and lead to out-of-bounds slices. The update also includes multiple feature additions, localization support, and various fixes unrelated to security. No known exploits are reported. The update is provided by the SUSE Product Security Team.

Impact

The integer overflow vulnerability could lead to memory corruption via out-of-bounds slices, which may impact application stability or security depending on usage context. No active exploitation is known. Other changes in the update do not affect security.

Summary

The forgejo-cli update fixes CVE-2026-25541, an integer overflow in BytesMut::reserve within the vendored bytes crate version 1.12.1. This overflow could corrupt the internal capacity tracking, potentially causing out-of-bounds slice access. The update also introduces localization support and numerous functional improvements and bug fixes. No cloud service is involved, and no exploit activity is reported. The vendor has released this update to address the vulnerability.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 17 Sep 2026, 02:08 UTC

Technical details

References

Community reviews

Related threats