Bug 2530051 (CVE-2026-87051) - CVE-2026-87051 operator-foundry: operator-foundry: resolveAndValidatePath performs lexical containment only — symlinks can escape the build context
Summary: CVE-2026-87051 operator-foundry: operator-foundry: resolveAndValidatePath per...
Keywords:
Status: NEW
Alias: CVE-2026-87051
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-08 19:05 UTC by OSIDB Bzimport
Modified: 2026-09-08 19:47 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-08 19:05:45 UTC
## resolveAndValidatePath performs lexical containment only — symlinks can escape the build context

**Component:** operator-foundry

The path-containment check used to confine build-context file access performs only lexical (string-based) validation of the resolved absolute path. It does not resolve symlinks before the containment check, so a symlink inside the build context can point outside of it and escape the intended confinement.

### Remediation
After computing `candidateAbs`, call `filepath.EvalSymlinks(candidateAbs)` (and `filepath.EvalSymlinks(ctxAbs)`) and re-run the `filepath.Rel`/`..` check on the resolved real paths; alternatively use `os.Root` (Go 1.24+) / `securejoin` to open the build context as a confinement root.

---
*Source: Ex-Wing/Glasswing Konflux CI security assessment (Mythos), finding FIND-003*


Note You need to log in before you can comment on or make changes to this bug.