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

CVE-2026-33553

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

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
Northern.tech CFEngine Enterprise 3.24.3 before 3.24.4 and 3.27.0 before 3.27.1 allows XSS.

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

Cross-site scripting (XSS) vulnerability in Northern.tech CFEngine Enterprise versions 3.24.3 before 3.24.4 and 3.27.0 before 3.27.1 allows attackers to inject malicious scripts through the application interface.

MitigationUpgrade CFEngine Enterprise to version 3.24.4, 3.27.1, or later to obtain the security patch for this XSS vulnerability.

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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. Confirm CFEngine Enterprise is installed
    Run 'cf-agent --version' or check for /var/cfengine directory existence on the server
    Affected if CFEngine Enterprise is not present on the system
  2. Identify the installed CFEngine Enterprise version
    Execute 'cf-promises --version' or check the version file in /var/cfengine (often in core/version or similar)
    Affected if Version is 3.24.3 or 3.27.0 specifically
  3. Compare installed version against affected ranges
    Compare your installed version number to the vulnerable versions (3.24.3, 3.27.0) and fixed versions (3.24.4, 3.27.1)
    Affected if Installed version equals 3.24.3 or 3.27.0 exactly (versions between 3.24.3 and 3.24.4, or between 3.27.0 and 3.27.1, are not valid release versions)
  4. Verify the web interface is enabled
    Check if the CFEngine Enterprise hub (web UI) is running by accessing the web interface URL or checking for httpd/cfengine-hub processes
    Affected if The web interface is accessible and running; the XSS vulnerability exists in this component

You are affected if CFEngine Enterprise version 3.24.3 or 3.27.0 is installed and the web interface is accessible.

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 CFEngine Enterprise to version 3.24.4, 3.27.1, or later to obtain the security patch for this XSS vulnerability.

Recommended fix Moderate confidence

CFEngine Enterprise 3.24.4 or 3.27.1 (depending on your current version branch)

  1. Identify current CFEngine Enterprise version using 'cf-promises -V' or 'cf-agent --version'
  2. If running 3.24.x, plan upgrade to version 3.24.4 or later
  3. If running 3.27.x, plan upgrade to version 3.27.1 or later
  4. If running an earlier version, upgrade to the nearest fixed version (3.24.4 or 3.27.1)
  5. Review CFEngine Enterprise release notes for the target version for any migration requirements
  6. Test upgrade in non-production environment before deploying to production
  7. Schedule maintenance window and apply upgrade to production systems
  8. Verify successful upgrade and confirm vulnerability is remediated
Caveat Review release notes for potential configuration or policy syntax changes between versions

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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