dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-8296

MEDIUM · 5.6 CVSS v4.0 Published 2026-06-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable

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
In affected versions of Octopus Server with certain access levels it was possible to embed a Cross-Site Scripting Payload via artifacts.

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 · moderate confidence

This is a stored Cross-Site Scripting (XSS) vulnerability in Octopus Server where users with specific access levels can embed malicious JavaScript payloads through the artifact upload functionality. When other users view these artifacts, the embedded script executes in their browser context, potentially allowing session hijacking or data theft.

MitigationUpgrade to a patched version of Octopus Server. Additionally, implement output encoding/sanitization on artifact content before rendering and restrict artifact upload permissions to the minimum necessary roles.

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
High
Privileges
High
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Confirm Octopus Server is deployed
    Identify if Octopus Server is running in your environment by checking for the Octopus service/process, or by accessing the Octopus web interface at your configured URL.
    Affected if Octopus Server is not installed or not in use - not affected.
  2. Identify installed Octopus Server version
    Log into the Octopus Web UI as an administrator, then go to Configuration > Nodes, or check the About page. Alternatively, check the installed package version via command line: octopusserver --version or inspect the installation directory for version metadata.
    Affected if The installed version falls within the range of versions known to be vulnerable (compare against Octopus security advisories for CVE-2026-8296).
  3. Verify artifact upload feature is accessible
    Check if the Artifacts module is enabled in your Octopus deployment. Navigate to Infrastructure > Projects > [Select a Project] > Artifacts, or verify via API endpoint: GET /api/artifacts (requires authentication). Confirm the feature is not disabled via configuration.
    Affected if The Artifacts feature is disabled or inaccessible - vulnerability may not be exploitable.
  4. Review user roles with artifact upload permissions
    In Octopus UI, go to Configuration > Users > [select user] > Roles, or go to Configuration > Teams > [select team] > Roles. Check which roles include the 'Artifact.Create' permission.
    Affected if Users other than administrators or limited roles have artifact upload capability - broader attack surface exists.
  5. Inspect recent artifact uploads for suspicious content
    Query the artifact repository or database for recently uploaded files. Check artifact metadata for unusual file names, content types, or payloads. Use API: GET /api/artifacts and review artifact contents.
    Affected if Malicious JavaScript or HTML content is present in uploaded artifacts - indicates active exploitation or attempted exploitation.

You are affected if you are running a vulnerable version of Octopus Server (per Octopus security advisories) AND the Artifacts feature is enabled AND users with artifact upload permissions exist in your environment.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of Octopus Server. Additionally, implement output encoding/sanitization on artifact content before rendering and restrict artifact upload permissions to the minimum necessary roles.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8296 — 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-8296 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