dbcve.org
Link Following (Symlink)Weakness · CWE-59

CVE-2026-47833

MEDIUM · 6.1 CVSS v3.1 Published 2026-06-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
setupBpmLogs follows symlink for bpm.log open and chown — container-to-host privilege escalation via /etc/shadow. A compromised process inside a bpm container can cause root to chown an arbitrary host file to vcap and append bpm JSON log lines to it. The chown alone lets the attacker take ownership of /etc/shadow and read every password hash on the host via the read-only /etc bind mount. This is a container-to-host confidentiality break affecting every bpm-managed job. Affected versions: bpm-release, all versions prior to v1.4.30.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The setupBpmLogs script in bpm-release follows symlinks when opening and chowning the bpm.log file, allowing a compromised container process to manipulate root into chowning arbitrary host files (like /etc/shadow) to the vcap user, enabling password hash theft via the host's read-only /etc bind mount.

MitigationUpgrade bpm-release to v1.4.30 or later which fixes the symlink following vulnerability in setupBpmLogs.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify bpm-release installation
    Query the deployment for bpm-release using bosh CLI (bosh -t <target> releases) or inspect the deployment manifest for the bpm-release release name and version entry
    Affected if bpm-release is deployed with a version below 1.4.30
  2. Locate setupBpmLogs script
    Find the setupBpmLogs script within the bpm-release package directory structure, typically under jobs/bpm/bin/ or similar in the release
    Affected if The setupBpmLogs script exists and is present in the deployment
  3. Inspect script for symlink handling
    Examine the setupBpmLogs script contents for file operations on bpm.log that use open() or chown() without checking for symlinks first (look for patterns like open() or chown() directly on a log file path without symlink verification)
    Affected if The script performs file operations on bpm.log without symlink protection (O_NOFOLLOW missing or no symlink check before chown)
  4. Check for container environment with bind mounts
    Review the deployment configuration or container runtime settings to determine if containers have bind mounts exposing the host /etc directory
    Affected if The environment uses container bind mounts that expose host /etc to the container

A system is affected if it runs bpm-release version lower than 1.4.30 with the vulnerable setupBpmLogs script in a container environment that has bind mounts to host directories like /etc.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade bpm-release to v1.4.30 or later which fixes the symlink following vulnerability in setupBpmLogs.

Recommended fix High confidence

bpm-release v1.4.30

  1. Download bpm-release v1.4.30 or later from the Cloud Foundry bpm-release repository
  2. Update your deployment manifest to use bpm-release version v1.4.30
  3. Redeploy the bpm-release using your BOSH director or deployment tooling
  4. Verify the deployment completes successfully and the new version is running
  5. Confirm that the symlink vulnerability in setupBpmLogs is resolved by testing that log file operations no longer follow arbitrary symlinks

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47833 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47833 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data