Skip to content
VulniPulse
Low2.6Red Hat Linux

Low [CVE-2026-87064] GitHub workflows lack explicit least-privilege permissions blocks

This low-severity Red Hat Linux advisory covers CVE-2026-87064.

CVE-2026-87064 Published Sep 8, 2026Updated by vendor Sep 8, 2026
Affected products & platforms
Red Hat LinuxUnclassified
Open vendor advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

A flaw was found in konflux-operator-tasks. The GitHub workflows used by this component do not explicitly define their required permissions.

This oversight means the workflows may inherit default access tokens that grant broader privileges than intended. Such excessive permissions could potentially allow an attacker to gain unauthorized access or perform actions beyond the intended scope, leading to information disclosure or unauthorized modifications.

This could potentially allow for unintended access to repository contents if not explicitly scoped to least privilege, but does not affect the runtime security of deployed Konflux applications. Red Hat severity: Low — CVSS 2.6 (CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N).

Weakness: CWE-269.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.

Official advisory · high-confidence parse· fetched 59 minutes ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 59 minutes ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Explicitly define least-privilege permissions within GitHub workflows. Add `permissions: contents: read` at the top level of every workflow, including `go-ci.yaml`, and then grant narrower write scopes only where specifically required, such as `security-events: write` for SARIF upload. This ensures workflow tokens operate with the minimum necessary permissions, reducing the potential impact of a compromised workflow.

Official advisory · high-confidence parse· fetched 59 minutes ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.