cve.bz

CVE-2026-106503 linuxfoundation: Improper Handling of Case Sensitivity

8.1 highEPSS 0.5%Fix available

High (8.1) in linuxfoundation. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in @backstage/plugin-scaffolder-backend 3.3.1, 3.4.1, 4.0.3.

On this page
Backstage is an open framework for building developer portals. Prior to 3.3.1, 3.4.1, 4.0.3 and 4.1.0, the @backstage/plugin-scaffolder-backend package is affected by scaffolder action input authorization bypass. An authenticated user with access to affected Scaffolder templates could bypass configured action restrictions. Depending on integration credentials, this could grant unauthorized access to repositories and related source-control resources. This issue is fixed in versions 3.3.1, 3.4.1, 4.0.3 and 4.1.0.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 43rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-178 Improper Handling of Case Sensitivity
CWE-284 Improper Access Control
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-106503 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-106503?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-106503?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-106503 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
linuxfoundation:backstage/plugin-scaffolder-backendbefore 3.3.1
linuxfoundation:backstage/plugin-scaffolder-backendfrom 3.4.0 before 3.4.1
linuxfoundation:backstage/plugin-scaffolder-backendfrom 4.0.0 before 4.0.3
linuxfoundation:backstage/plugin-scaffolder-backendfrom 4.0.4 before 4.1.0
linuxfoundation:backstagebefore 1.49.6
linuxfoundation:backstagefrom 1.50.0 before 1.50.5
linuxfoundation:backstagefrom 1.51.0 before 1.54.6

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-hmp2-4m7g-22cvnpm@backstage/plugin-scaffolder-backend<3.3.13.3.1
GHSA-hmp2-4m7g-22cvnpm@backstage/plugin-scaffolder-backend>=3.4.0 <3.4.13.4.1
GHSA-hmp2-4m7g-22cvnpm@backstage/plugin-scaffolder-backend>=4.0.0 <4.0.34.0.3
GHSA-hmp2-4m7g-22cvnpm@backstage/plugin-scaffolder-backend>=4.0.4 <4.1.04.1.0

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as an Important severity because authenticated remote users can circumvent execution guardrails defined for backend actions, creating high confidentiality and integrity risks for connected source control management systems. In Red Hat Developer Hub and Ansible Automation Platform environments where software templates are enabled, users with permission to run Scaffolder tasks could manipulate input parameters beyond authorized boundaries. The overall exposure is determined by the privilege scope granted to underlying integration service accounts and tokens.

Red Hat's mitigation

To reduce the risk associated with this flaw:

1. Restrict template access: Limit permissions to execute Scaffolder templates to trusted users by configuring role-based access control (RBAC) policies in Red Hat Developer Hub or Ansible Automation Platform.

2. Enforce least privilege on integration credentials: Audit and restrict source control provider tokens (such as GitHub, GitLab, or Bitbucket credentials) to the minimum necessary repository scopes and permissions required for legitimate template actions.

Caveats: Limiting integration credential permissions may cause templates that require administrative or elevated privileges to fail. Modifying credential secrets or configuration files within the deployment environment will require restarting the application pods for the new settings to take effect.

ProductPackageStateAdvisory
Red Hat Ansible Automation Platform 2.2ansible-automation-platform/automation-portal:1792523640Fixed 2026-10-21RHSA-2026:86675
Red Hat Developer Hub 1.10rhdh/rhdh-hub-rhel9:1794341043Fixed 2026-11-11RHSA-2026:99044
Red Hat Developer Hub 1rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backendAffected
Self-service automation portal 2ansible-automation-platform/bootc-automation-portal-rhel9Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-106503.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-284 (17).

References

Check your stackJSON