CVE-2026-56004
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 · uneditedA shellcode injection in the mercurial handler of the obs tar_scm source service before version 0.12.4 could be used by attackers able to provide a _service file to execute code as the source service or the local user checking out the malicious services
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 confidenceA shellcode injection vulnerability exists in the mercurial handler of the obs tar_scm source service, allowing attackers who can provide a malicious _service file to execute arbitrary code either as the source service user or as the local user checking out the affected services.
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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if obs tar_scm source service is installedCheck for the presence of the obs tar_scm package or source service components on the system. Look for package manager entries or source service directories.Affected if obs tar_scm is installed and in use as a source service
-
Determine the installed version of obs tar_scmQuery the package manager for the installed version of obs tar_scm (e.g., rpm -q, dpkg -l, or gem list for ruby packages) and compare it to version 0.12.4Affected if The installed version is earlier than 0.12.4 or the version cannot be determined (unknown) and obs tar_scm is present
-
Check for mercurial handler usage in _service filesInspect any _service files in build service projects or source repositories. Look for <service name="tar_scm"> entries that specify <param name="scm">mercurial</param> or similar mercurial-related parameters.Affected if _service files exist that configure tar_scm with mercurial as the SCM source
-
Verify source validation for _service filesReview the build service configuration to determine whether _service files are sourced from untrusted or external repositories without validation.Affected if _service files can be provided by untrusted parties or are not validated before use
A user is affected if obs tar_scm with mercurial handler is installed with a version earlier than 0.12.4 and processes _service files from sources that are not trusted or validated.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade obs tar_scm source service to version 0.12.4 or later to remediate this vulnerability. Additionally, restrict and validate _service file sources to prevent untrusted parties from injecting malicious content.
version 0.12.4 or later
- 1. Identify the obs-tar_scm source service installation in your environment
- 2. Check the current installed version of the tar_scm package
- 3. Upgrade the tar_scm package to version 0.12.4 or later
- 4. Verify the upgrade was successful by checking the installed version
- 5. Review any _service files in use to ensure they were not maliciously modified
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-56004 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-56004 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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