PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-89151 Forgejo CVE debrief

CVE-2026-89151 is a low-severity vulnerability in Forgejo before version 16.0.4 that allows the use of restricted API tokens for unintended access to the 'allow maintainer edit' feature. Defenders should assess exposure, particularly those managing Forgejo instances or maintaining code repositories. The vulnerability's impact is limited, but verification of affected versions and remediation priority are necessary.

Vendor
Forgejo
Product
Unknown
CVSS
LOW 3.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-11
Original CVE updated
2026-09-11
Advisory published
2026-09-11
Advisory updated
2026-09-11

Who should care

Defenders managing Forgejo instances, maintainers of code repositories, and those responsible for vulnerability management should assess exposure and prioritize remediation based on their deployment context.

Why it matters

CVE-2026-89151 is a low-severity vulnerability in Forgejo that requires verification of affected versions and remediation priority based on deployment context.

  • Verification of affected Forgejo versions is required
  • Remediation priority should be set based on deployment context
  • Monitoring for potential misuse of restricted API tokens is necessary
  • Limited impact on code repository management is possible

Technical summary

The vulnerability allows the use of restricted API tokens for unintended access to the 'allow maintainer edit' feature in Forgejo before version 16.0.4. This could potentially lead to limited impact on code repository management. Defenders should verify if their Forgejo instances are affected and prioritize remediation based on their deployment context, considering verification of affected versions and remediation priority. It requires verification of affected Forgejo versions and remediation priority based on deployment context, with monitoring for potential misu

Defensive priority

Defenders should verify if their Forgejo instances are affected and prioritize remediation based on their deployment context.

Recommended defensive actions

  • Verify if the Forgejo instance is affected by checking the version
  • Assess exposure based on deployment context
  • Prioritize remediation based on the low-severity impact
  • Monitor for potential misuse of restricted API tokens

Evidence notes

The CVE record and NVD entry provide limited information about the vulnerability. Further verification is required to determine affected versions and remediation steps.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-89151 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-89151

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-89151 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-89151

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.