Common Weakness Enumeration

CWE-862

Allowed-with-Review

Missing Authorization

Abstraction: Class · Status: Incomplete

The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

14809 vulnerabilities reference this CWE, most recent first.

GHSA-5V56-6X55-VHPV

Vulnerability from github – Published: 2026-01-09 18:31 – Updated: 2026-01-09 18:31
VLAI
Details

Missing Authorization vulnerability in Wikimedia Foundation MediaWiki - CampaignEvents extension allows Privilege Abuse.This issue affects MediaWiki - CampaignEvents extension: 1.45, 1.44, 1.43, 1.39.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-0817"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-01-09T16:16:08Z",
    "severity": "MODERATE"
  },
  "details": "Missing Authorization vulnerability in Wikimedia Foundation MediaWiki - CampaignEvents extension allows Privilege Abuse.This issue affects MediaWiki - CampaignEvents extension: 1.45, 1.44, 1.43, 1.39.",
  "id": "GHSA-5v56-6x55-vhpv",
  "modified": "2026-01-09T18:31:36Z",
  "published": "2026-01-09T18:31:36Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-0817"
    },
    {
      "type": "WEB",
      "url": "https://gerrit.wikimedia.org/r/q/I7ed0049691258c8bd2555e599b9b88490fbe3358"
    },
    {
      "type": "WEB",
      "url": "https://phabricator.wikimedia.org/T410560"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-5V8G-2W9G-6CWM

Vulnerability from github – Published: 2026-05-26 13:30 – Updated: 2026-05-26 13:30
VLAI
Details

Missing Authorization vulnerability in Ruben Garcia GamiPress allows Exploiting Incorrectly Configured Access Control Security Levels.

This issue affects GamiPress: from n/a through 7.6.3.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-24546"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-05-25T20:16:36Z",
    "severity": "MODERATE"
  },
  "details": "Missing Authorization vulnerability in Ruben Garcia GamiPress allows Exploiting Incorrectly Configured Access Control Security Levels.\n\nThis issue affects GamiPress: from n/a through 7.6.3.",
  "id": "GHSA-5v8g-2w9g-6cwm",
  "modified": "2026-05-26T13:30:49Z",
  "published": "2026-05-26T13:30:49Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-24546"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/wordpress/plugin/gamipress/vulnerability/wordpress-gamipress-plugin-7-6-3-broken-access-control-vulnerability?_s_id=cve"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-5V99-78FJ-WC52

Vulnerability from github – Published: 2023-01-26 21:30 – Updated: 2023-02-01 21:30
VLAI
Details

In getMainActivityLaunchIntent of LauncherAppsService.java, there is a possible way to bypass the restrictions on starting activities from the background due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-12 Android-12LAndroid ID: A-229256049

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2023-20916"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2023-01-26T21:18:00Z",
    "severity": "HIGH"
  },
  "details": "In getMainActivityLaunchIntent of LauncherAppsService.java, there is a possible way to bypass the restrictions on starting activities from the background due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-12 Android-12LAndroid ID: A-229256049",
  "id": "GHSA-5v99-78fj-wc52",
  "modified": "2023-02-01T21:30:23Z",
  "published": "2023-01-26T21:30:20Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-20916"
    },
    {
      "type": "WEB",
      "url": "https://source.android.com/security/bulletin/2023-01-01"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-5VFC-VCPR-H92W

Vulnerability from github – Published: 2025-12-09 18:30 – Updated: 2026-01-20 15:32
VLAI
Details

Missing Authorization vulnerability in paysera WooCommerce Payment Gateway – Paysera woo-payment-gateway-paysera allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WooCommerce Payment Gateway – Paysera: from n/a through <= 3.9.0.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2025-63015"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-12-09T16:18:06Z",
    "severity": "MODERATE"
  },
  "details": "Missing Authorization vulnerability in paysera WooCommerce Payment Gateway \u0026#8211; Paysera woo-payment-gateway-paysera allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WooCommerce Payment Gateway \u0026#8211; Paysera: from n/a through \u003c= 3.9.0.",
  "id": "GHSA-5vfc-vcpr-h92w",
  "modified": "2026-01-20T15:32:03Z",
  "published": "2025-12-09T18:30:39Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-63015"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/Wordpress/Plugin/woo-payment-gateway-paysera/vulnerability/wordpress-woocommerce-payment-gateway-paysera-plugin-3-9-0-broken-access-control-vulnerability?_s_id=cve"
    },
    {
      "type": "WEB",
      "url": "https://vdp.patchstack.com/database/Wordpress/Plugin/woo-payment-gateway-paysera/vulnerability/wordpress-woocommerce-payment-gateway-paysera-plugin-3-9-0-broken-access-control-vulnerability?_s_id=cve"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-5VH6-VPRX-FJVM

Vulnerability from github – Published: 2023-07-06 21:14 – Updated: 2024-04-04 05:40
VLAI
Details

Vendor Master Hierarchy - versions SAP_APPL 500, SAP_APPL 600, SAP_APPL 602, SAP_APPL 603, SAP_APPL 604, SAP_APPL 605, SAP_APPL 606, SAP_APPL 616, SAP_APPL 617, SAP_APPL 618, S4CORE 100, does not perform necessary authorization checks for an authenticated user to access some of its function. This could lead to modification of data impacting the integrity of the system.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2023-32112"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2023-05-09T02:15:12Z",
    "severity": "MODERATE"
  },
  "details": "Vendor Master Hierarchy - versions SAP_APPL 500, SAP_APPL 600, SAP_APPL 602, SAP_APPL 603, SAP_APPL 604, SAP_APPL 605, SAP_APPL 606, SAP_APPL 616, SAP_APPL 617, SAP_APPL 618, S4CORE 100, does not perform necessary authorization checks for an authenticated user to\u00a0access some of its function. This could lead to modification of data impacting the integrity of the system.\n\n",
  "id": "GHSA-5vh6-vprx-fjvm",
  "modified": "2024-04-04T05:40:58Z",
  "published": "2023-07-06T21:14:55Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-32112"
    },
    {
      "type": "WEB",
      "url": "https://launchpad.support.sap.com/#/notes/2335198"
    },
    {
      "type": "WEB",
      "url": "https://www.sap.com/documents/2022/02/fa865ea4-167e-0010-bca6-c68f7e60039b.html"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-5VHV-M5CH-WX48

Vulnerability from github – Published: 2024-05-18 09:30 – Updated: 2024-05-18 09:30
VLAI
Details

The Contact Form Plugin by Fluent Forms for Quiz, Survey, and Drag & Drop WP Form Builder plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the /wp-json/fluentform/v1/global-settings REST API endpoint in all versions up to, and including, 5.1.16. This makes it possible for unauthenticated attackers to modify all of the plugin's settings.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2024-2782"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-05-18T08:15:07Z",
    "severity": "HIGH"
  },
  "details": "The Contact Form Plugin by Fluent Forms for Quiz, Survey, and Drag \u0026 Drop WP Form Builder plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the /wp-json/fluentform/v1/global-settings REST API endpoint in all versions up to, and including, 5.1.16. This makes it possible for unauthenticated attackers to modify all of the plugin\u0027s settings.",
  "id": "GHSA-5vhv-m5ch-wx48",
  "modified": "2024-05-18T09:30:47Z",
  "published": "2024-05-18T09:30:47Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-2782"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/changeset/3088078/fluentform/trunk/app/Http/Policies/GlobalSettingsPolicy.php"
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/0814e7b3-404a-4db5-b564-46c9086ec048?source=cve"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-5VJ6-HF6F-9VPW

Vulnerability from github – Published: 2025-09-22 21:30 – Updated: 2026-04-01 18:36
VLAI
Details

Missing Authorization vulnerability in Christiaan Pieterse MaxiBlocks allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects MaxiBlocks: from n/a through 2.1.3.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2025-58968"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-09-22T19:16:22Z",
    "severity": "MODERATE"
  },
  "details": "Missing Authorization vulnerability in Christiaan Pieterse MaxiBlocks allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects MaxiBlocks: from n/a through 2.1.3.",
  "id": "GHSA-5vj6-hf6f-9vpw",
  "modified": "2026-04-01T18:36:18Z",
  "published": "2025-09-22T21:30:28Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-58968"
    },
    {
      "type": "WEB",
      "url": "https://patchstack.com/database/wordpress/plugin/maxi-blocks/vulnerability/wordpress-maxiblocks-plugin-2-1-3-broken-access-control-vulnerability?_s_id=cve"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-5VJG-9HJQ-57M8

Vulnerability from github – Published: 2023-03-10 21:30 – Updated: 2026-04-08 18:32
VLAI
Details

The RapidLoad Power-Up for Autoptimize plugin for WordPress is vulnerable to unauthorized settings update due to a missing capability check on the uucss_update_rule function in versions up to, and including, 1.7.1. This makes it possible for authenticated attackers with subscriber-level access to update caching rules.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2023-1339"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2023-03-10T20:15:00Z",
    "severity": "MODERATE"
  },
  "details": "The RapidLoad Power-Up for Autoptimize plugin for WordPress is vulnerable to unauthorized settings update due to a missing capability check on the uucss_update_rule function in versions up to, and including, 1.7.1. This makes it possible for authenticated attackers with subscriber-level access to update caching rules.",
  "id": "GHSA-5vjg-9hjq-57m8",
  "modified": "2026-04-08T18:32:03Z",
  "published": "2023-03-10T21:30:24Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-1339"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/changeset/2877726/unusedcss/trunk/includes/modules/unused-css/UnusedCSS_Admin.php?contextall=1\u0026old=2847136\u0026old_path=%2Funusedcss%2Ftrunk%2Fincludes%2Fmodules%2Funused-css%2FUnusedCSS_Admin.php"
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/19f126f8-1d59-44b5-8e0e-c37f1fbedf5a"
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/19f126f8-1d59-44b5-8e0e-c37f1fbedf5a?source=cve"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-5VQG-GQHG-CW89

Vulnerability from github – Published: 2026-01-09 09:31 – Updated: 2026-01-09 09:31
VLAI
Details

The Frontend Admin by DynamiApps plugin for WordPress is vulnerable to missing authorization to unauthorized data modification and deletion due to a missing capability check on the 'delete_object' function in all versions up to, and including, 3.28.25. This makes it possible for unauthenticated attackers to delete arbitrary posts, pages, products, taxonomy terms, and user accounts.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2025-14741"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-01-09T08:15:57Z",
    "severity": "CRITICAL"
  },
  "details": "The Frontend Admin by DynamiApps plugin for WordPress is vulnerable to missing authorization to unauthorized data modification and deletion due to a missing capability check on the \u0027delete_object\u0027 function in all versions up to, and including, 3.28.25. This makes it possible for unauthenticated attackers to delete arbitrary posts, pages, products, taxonomy terms, and user accounts.",
  "id": "GHSA-5vqg-gqhg-cw89",
  "modified": "2026-01-09T09:31:20Z",
  "published": "2026-01-09T09:31:20Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-14741"
    },
    {
      "type": "WEB",
      "url": "https://plugins.trac.wordpress.org/browser/acf-frontend-form-element/tags/3.28.26/main/frontend/fields/general/class-delete-object.php?marks=106,119,132,142#L106"
    },
    {
      "type": "WEB",
      "url": "https://www.wordfence.com/threat-intel/vulnerabilities/id/53adbab6-953a-4a6f-bbfc-89efdbdd28e0?source=cve"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-5VVM-67PJ-72G4

Vulnerability from github – Published: 2026-02-19 15:16 – Updated: 2026-02-23 22:21
VLAI
Summary
Kargo has Missing Authorization Vulnerabilities in Approval & Promotion REST API Endpoints
Details

Summary

Kargo's authorization model includes a promote verb -- a non-standard Kubernetes "dolphin verb" -- that gates the ability to advance Freight through a promotion pipeline. This verb exists to separate the ability to manage promotion-related resources from the ability to trigger promotions, enabling fine-grained access control over what is often a sensitive operation.

The promote verb is correctly enforced in Kargo's legacy gRPC API. However, three endpoints in the newer REST API omit this check, relying only on standard Kubernetes RBAC for the underlying resource operations (patch on freights/status or create on promotions). This permits users who hold those standard permissions -- but who were deliberately not granted promote -- to bypass the intended authorization boundary.

The affected endpoints are:

  1. POST /v1beta1/projects/{project}/freight/{freight}/approve

    Approves Freight for promotion to a specific Stage.

    The endpoint is intended to require both patch permission on Freight status and promote permission on the target Stage, but asserts only the former.

  2. POST /v1beta1/projects/{project}/stages/{stage}/promotions

    Promotes Freight to a specific Stage.

    The endpoint is intended to require both create permission on Promotion resources and promote permission on the target Stage, but asserts only the former.

  3. POST /v1beta1/projects/{project}/stages/{stage}/promotions/downstream

    Promotes Freight to all Stages immediately downstream of a given Stage.

    The endpoint is intended to require both create permission on Promotion resources and promote permission on each downstream Stage, but asserts only the former.

Base Metrics

The following sections provide the rationale for the values selected for each of CVSS v4's base metrics.

Attack Vector (AV): Network

The affected endpoints are part of Kargo's newer REST API, which is served over HTTP/HTTPS. (The analogous endpoints of the legacy gRPC API correctly check promote permission and are not affected.) No local or physical access is required.

Attack Complexity (AC): Low

The attack requires only well-formed API requests to the affected endpoints.

Attack Requirements (AT): None

No specific environmental conditions are required beyond those that are typical for any Kargo instance.

Privileges Required (PR): Low

The attacker must hold permissions to patch Freight status and/or create Promotion resources. These are standard operational permissions commonly granted to some Kargo users and do not represent what CVSS formally considers administrative or elevated access.

User Interaction (UI): None

The attack is fully automated via API calls. No other user needs to take any action.

Confidentiality Impact to Vulnerable System (VC): None

The vulnerability does not expose any data from the Kargo control plane.

Integrity Impact to Vulnerable System (VI): Low

The attacker can coerce a Stage into a state it might not otherwise transition to. This constitutes bounded state corruption within a single Project. Kargo itself continues to function correctly.

Availability Impact to Vulnerable System (VA): None

Promotion resources created by exploitation of this vulnerability consume the same controller resources as a legitimate Promotion would. A user with proper promote permissions could generate identical load. The vulnerability does not introduce any new avenue for resource exhaustion.

Confidentiality Impact to Subsequent Systems (SC): None

The vulnerability does not provide any mechanism for the attacker to read data from downstream systems.

Integrity Impact to Subsequent Systems (SI): Low

Critically, the attacker does not control the content of Freight resources without artifact repositories also having been compromised. In isolation, which is how vulnerabilities are scored, the worst consequence of a successful attack is downstream systems (e.g. Argo CD) deploying incorrect revisions of artifacts, which in some cases should have been rejected by bypassed segments of the promotion pipeline. Though the operational consequences land on subsequent systems, they are bounded by the attacker's inability to inject arbitrary content.

Availability Impact to Subsequent Systems (SA): None

The attack does not provide any mechanism to degrade the availability of downstream systems beyond what could be achieved with legitimately promoted Freight.

Mitigating Factors

  • Only the REST API endpoints introduced in v1.9.0 are affected. The legacy gRPC API and the Kargo UI (which uses the gRPC API) correctly enforce the promote permission check and are not vulnerable.

  • The window of affected versions is narrow: v1.9.0 through v1.9.2.

  • Exploitation requires authentication to the Kargo API server and specific operational permissions (patch on freights/status or create on promotions). Anonymous or minimally privileged users cannot exploit this vulnerability.

  • Impact is bounded to a single Project. The promote bypass does not enable cross-Project access or escalation beyond the namespace in which the attacker already holds the prerequisite permissions.

  • There is no evidence of exploitation in the wild.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/akuity/kargo"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "1.9.0"
            },
            {
              "fixed": "1.9.3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-27111"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-862"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-02-19T15:16:31Z",
    "nvd_published_at": "2026-02-20T22:16:29Z",
    "severity": "MODERATE"
  },
  "details": "## Summary\n\nKargo\u0027s authorization model includes a `promote` verb -- a non-standard Kubernetes [\"dolphin verb\"](https://www.aquasec.com/blog/kubernetes-verbs/) -- that gates the ability to advance `Freight` through a promotion pipeline. This verb exists to separate the ability to _manage_ promotion-related resources from the ability to _trigger_ promotions, enabling fine-grained access control over what is often a sensitive operation.\n\nThe `promote` verb is correctly enforced in Kargo\u0027s legacy gRPC API. However, three endpoints in the newer REST API omit this check, relying only on standard Kubernetes RBAC for the underlying resource operations (`patch` on `freights/status` or `create` on `promotions`). This permits users who hold those standard permissions -- but who were deliberately _not_ granted `promote` -- to bypass the intended authorization boundary.\n\nThe affected endpoints are:\n\n1. `POST /v1beta1/projects/{project}/freight/{freight}/approve`\n\n    Approves `Freight` for promotion to a specific `Stage`.\n\n    The endpoint is intended to require both `patch` permission on `Freight` status and `promote` permission on the target `Stage`, but asserts only the former.\n\n2. `POST /v1beta1/projects/{project}/stages/{stage}/promotions`\n\n    Promotes `Freight` to a specific `Stage`.\n\n    The endpoint is intended to require both `create` permission on `Promotion` resources and `promote` permission on the target `Stage`, but asserts only the former.\n\n3. `POST /v1beta1/projects/{project}/stages/{stage}/promotions/downstream`\n\n    Promotes `Freight` to all `Stage`s immediately downstream of a given `Stage`.\n\n    The endpoint is intended to require both `create` permission on `Promotion` resources and `promote` permission on each downstream `Stage`, but asserts only the former.\n\n## Base Metrics\n\nThe following sections provide the rationale for the values selected for each of CVSS v4\u0027s base metrics.\n\n### Attack Vector (AV): Network\n\nThe affected endpoints are part of Kargo\u0027s newer REST API, which is served over HTTP/HTTPS. (The analogous endpoints of the legacy gRPC API correctly check `promote` permission and are not affected.) No local or physical access is required.\n\n### Attack Complexity (AC): Low\n\nThe attack requires only well-formed API requests to the affected endpoints.\n\n### Attack Requirements (AT): None\n\nNo specific environmental conditions are required beyond those that are typical for any Kargo instance.\n\n### Privileges Required (PR): Low\n\nThe attacker must hold permissions to patch `Freight` status and/or create `Promotion` resources. These are standard operational permissions commonly granted to some Kargo users and do not represent what CVSS formally considers administrative or elevated access.\n\n### User Interaction (UI): None\n\nThe attack is fully automated via API calls. No other user needs to take any action.\n\n### Confidentiality Impact to Vulnerable System (VC): None\n\nThe vulnerability does not expose any data from the Kargo control plane.\n\n### Integrity Impact to Vulnerable System (VI): Low\n\nThe attacker can coerce a `Stage` into a state it might not otherwise transition to. This constitutes bounded state corruption within a single Project. Kargo itself continues to function correctly.\n\n### Availability Impact to Vulnerable System (VA): None\n\n`Promotion` resources created by exploitation of this vulnerability consume the same controller resources as a legitimate `Promotion` would. A user with proper `promote` permissions could generate identical load. The vulnerability does not introduce any new avenue for resource exhaustion.\n\n### Confidentiality Impact to Subsequent Systems (SC): None\n\nThe vulnerability does not provide any mechanism for the attacker to read data from downstream systems.\n\n### Integrity Impact to Subsequent Systems (SI): Low\n\nCritically, the attacker does not control the _content_ of `Freight` resources without artifact repositories also having been compromised. In isolation, which is how vulnerabilities are scored, the worst consequence of a successful attack is downstream systems (e.g. Argo CD) deploying incorrect revisions of artifacts, which in some cases should have been rejected by bypassed segments of the promotion pipeline. Though the operational consequences land on subsequent systems, they are bounded by the attacker\u0027s inability to inject arbitrary content.\n\n### Availability Impact to Subsequent Systems (SA): None\n\nThe attack does not provide any mechanism to degrade the availability of downstream systems beyond what could be achieved with legitimately promoted `Freight`.\n\n## Mitigating Factors\n\n- Only the REST API endpoints introduced in v1.9.0 are affected. The legacy gRPC API and the Kargo UI (which uses the gRPC API) correctly enforce the `promote` permission check and are not vulnerable.\n\n- The window of affected versions is narrow: v1.9.0 through v1.9.2.\n\n- Exploitation requires authentication to the Kargo API server and specific operational permissions (`patch` on `freights/status` or `create` on `promotions`). Anonymous or minimally privileged users cannot exploit this vulnerability.\n\n- Impact is bounded to a single Project. The `promote` bypass does not enable cross-Project access or escalation beyond the namespace in which the attacker already holds the prerequisite permissions.\n\n- There is no evidence of exploitation in the wild.",
  "id": "GHSA-5vvm-67pj-72g4",
  "modified": "2026-02-23T22:21:12Z",
  "published": "2026-02-19T15:16:31Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/akuity/kargo/security/advisories/GHSA-5vvm-67pj-72g4"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-27111"
    },
    {
      "type": "WEB",
      "url": "https://github.com/akuity/kargo/commit/833314cad5513d48d89431493325ae44c1324a49"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/akuity/kargo"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Kargo has Missing Authorization Vulnerabilities in Approval \u0026 Promotion REST API Endpoints"
}

Mitigation
Architecture and Design
  • Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries.
  • Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
Mitigation
Architecture and Design

Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].

Mitigation MIT-4.4
Architecture and Design

Strategy: Libraries or Frameworks

  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
Mitigation
Architecture and Design
  • For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page.
  • One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
Mitigation
System Configuration Installation

Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.

CAPEC-665: Exploitation of Thunderbolt Protection Flaws

An adversary leverages a firmware weakness within the Thunderbolt protocol, on a computing device to manipulate Thunderbolt controller firmware in order to exploit vulnerabilities in the implementation of authorization and verification schemes within Thunderbolt protection mechanisms. Upon gaining physical access to a target device, the adversary conducts high-level firmware manipulation of the victim Thunderbolt controller SPI (Serial Peripheral Interface) flash, through the use of a SPI Programing device and an external Thunderbolt device, typically as the target device is booting up. If successful, this allows the adversary to modify memory, subvert authentication mechanisms, spoof identities and content, and extract data and memory from the target device. Currently 7 major vulnerabilities exist within Thunderbolt protocol with 9 attack vectors as noted in the Execution Flow.