Common Weakness Enumeration

CWE-287

Discouraged

Improper Authentication

Abstraction: Class · Status: Draft

API response cwe.mitre.org

When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

5960 vulnerabilities reference this CWE, most recent first.

GHSA-5CV7-H7GR-WJGH

Vulnerability from github – Published: 2026-05-13 21:32 – Updated: 2026-05-13 21:32
VLAI
Details

An Editor can overwrite a dashboard not owned by them to acquire admin on that specific dashboard. The user must have write access to the dashboard to escalate privilege.

Severity
7.1 (High)
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2026-33377"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-284",
      "CWE-287"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-05-13T20:16:20Z",
    "severity": "HIGH"
  },
  "details": "An Editor can overwrite a dashboard not owned by them to acquire admin on that specific dashboard. The user must have write access to the dashboard to escalate privilege.",
  "id": "GHSA-5cv7-h7gr-wjgh",
  "modified": "2026-05-13T21:32:06Z",
  "published": "2026-05-13T21:32:06Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-33377"
    },
    {
      "type": "WEB",
      "url": "https://grafana.com/security/security-advisories/cve-2026-33377"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-5CWM-XW7V-FMP2

Vulnerability from github – Published: 2023-11-13 18:30 – Updated: 2023-11-13 18:30
VLAI
Details

Improper access control vulnerability in SmsController prior to SMR Nov-2023 Release1 allows attacker to bypass restrictions on starting activities from the background.

Severity
9.8 (Critical)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2023-42531"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-287"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2023-11-07T08:15:15Z",
    "severity": "CRITICAL"
  },
  "details": "Improper access control vulnerability in SmsController prior to SMR Nov-2023 Release1 allows attacker to bypass restrictions on starting activities from the background.",
  "id": "GHSA-5cwm-xw7v-fmp2",
  "modified": "2023-11-13T18:30:59Z",
  "published": "2023-11-13T18:30:59Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2023-42531"
    },
    {
      "type": "WEB",
      "url": "https://security.samsungmobile.com/securityUpdate.smsb?year=2023\u0026month=11"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-5CX5-WH4M-82FH

Vulnerability from github – Published: 2026-03-19 17:56 – Updated: 2026-03-27 21:57
VLAI
Summary
MinIO has JWT Algorithm Confusion in OIDC Authentication
Details

Impact

What kind of vulnerability is it? Who is impacted?

A JWT algorithm confusion vulnerability in MinIO's OpenID Connect authentication allows an attacker who knows the OIDC ClientSecret to forge arbitrary identity tokens and obtain S3 credentials with any policy, including consoleAdmin.

An attacker with knowledge of the OIDC ClientSecret can:

  • Impersonate any user identity
  • Obtain S3 credentials with any IAM policy, including consoleAdmin
  • Access, modify, or delete any data in the MinIO deployment

The attack is deterministic (100% success rate, no race conditions).

Attack Prerequisites

The attacker must know the OIDC ClientSecret. While this is a shared credential (not a private key), it is more accessible than commonly assumed:

  • CVE-2023-28432 previously leaked environment variables including MINIO_IDENTITY_OPENID_CLIENT_SECRET
  • Client secrets are often present in frontend OAuth configurations, mobile app bundles, CI/CD pipelines, and shared configuration files
  • In many organizations, the client secret is accessible to operators and engineers who should not be able to forge arbitrary identities

Affected Versions

All MinIO releases from RELEASE.2022-11-08T05-27-07Z through the final release of the minio/minio open-source project.

Patches

Fixed in: MinIO AIStor RELEASE.2026-03-17T21-25-16Z

Downloads

Binary Downloads

Platform Architecture Download
Linux amd64 minio
Linux arm64 minio
macOS arm64 minio
macOS amd64 minio
Windows amd64 minio.exe

FIPS Binaries

Platform Architecture Download
Linux amd64 minio.fips
Linux arm64 minio.fips

Package Downloads

Format Architecture Download
DEB amd64 minio_20260317212516.0.0_amd64.deb
DEB arm64 minio_20260317212516.0.0_arm64.deb
RPM amd64 minio-20260317212516.0.0-1.x86_64.rpm
RPM arm64 minio-20260317212516.0.0-1.aarch64.rpm

Container Images

# Standard
docker pull quay.io/minio/aistor/minio:RELEASE.2026-03-17T21-25-16Z
podman pull quay.io/minio/aistor/minio:RELEASE.2026-03-17T21-25-16Z

# FIPS
docker pull quay.io/minio/aistor/minio:RELEASE.2026-03-17T21-25-16Z.fips
podman pull quay.io/minio/aistor/minio:RELEASE.2026-03-17T21-25-16Z.fips

Homebrew (macOS)

brew install minio/aistor/minio

Workarounds

Severity
9.2 (Critical)
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/minio/minio"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "last_affected": "0.0.0-20260212201848-7aac2a2c5b7c"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-33322"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-287",
      "CWE-327"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-03-19T17:56:37Z",
    "nvd_published_at": "2026-03-24T20:16:27Z",
    "severity": "CRITICAL"
  },
  "details": "### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nA JWT algorithm confusion vulnerability in MinIO\u0027s OpenID Connect authentication allows an attacker who knows the OIDC `ClientSecret` to forge arbitrary identity tokens and obtain S3 credentials with any policy, including `consoleAdmin`.\n\nAn attacker with knowledge of the OIDC `ClientSecret` can:\n\n- Impersonate any user identity\n- Obtain S3 credentials with any IAM policy, including `consoleAdmin`\n- Access, modify, or delete any data in the MinIO deployment\n\nThe attack is deterministic (100% success rate, no race conditions).\n\n#### Attack Prerequisites\n\nThe attacker must know the OIDC `ClientSecret`. While this is a shared credential (not a private key), it is more accessible than commonly assumed:\n\n- CVE-2023-28432 previously leaked environment variables including `MINIO_IDENTITY_OPENID_CLIENT_SECRET`\n- Client secrets are often present in frontend OAuth configurations, mobile app bundles, CI/CD pipelines, and shared configuration files\n- In many organizations, the client secret is accessible to operators and engineers who should not be able to forge arbitrary identities\n\n\n#### Affected Versions\n\nAll MinIO releases from `RELEASE.2022-11-08T05-27-07Z` through the final release of the `minio/minio` open-source project.\n\n### Patches\n\n**Fixed in:** MinIO AIStor `RELEASE.2026-03-17T21-25-16Z`\n\n## Downloads\n\n### Binary Downloads\n\n| Platform | Architecture | Download                                                                    |\n| -------- | ------------ | --------------------------------------------------------------------------- |\n| Linux    | amd64        | [minio](https://dl.min.io/aistor/minio/release/linux-amd64/minio)           |\n| Linux    | arm64        | [minio](https://dl.min.io/aistor/minio/release/linux-arm64/minio)           |\n| macOS    | arm64        | [minio](https://dl.min.io/aistor/minio/release/darwin-arm64/minio)          |\n| macOS    | amd64        | [minio](https://dl.min.io/aistor/minio/release/darwin-amd64/minio)          |\n| Windows  | amd64        | [minio.exe](https://dl.min.io/aistor/minio/release/windows-amd64/minio.exe) |\n\n### FIPS Binaries\n\n| Platform | Architecture | Download                                                                    |\n| -------- | ------------ | --------------------------------------------------------------------------- |\n| Linux    | amd64        | [minio.fips](https://dl.min.io/aistor/minio/release/linux-amd64/minio.fips) |\n| Linux    | arm64        | [minio.fips](https://dl.min.io/aistor/minio/release/linux-arm64/minio.fips) |\n\n### Package Downloads\n\n| Format | Architecture | Download                                                                                                                            |\n| ------ | ------------ | ----------------------------------------------------------------------------------------------------------------------------------- |\n| DEB    | amd64        | [minio_20260317212516.0.0_amd64.deb](https://dl.min.io/aistor/minio/release/linux-amd64/minio_20260317212516.0.0_amd64.deb)         |\n| DEB    | arm64        | [minio_20260317212516.0.0_arm64.deb](https://dl.min.io/aistor/minio/release/linux-arm64/minio_20260317212516.0.0_arm64.deb)         |\n| RPM    | amd64        | [minio-20260317212516.0.0-1.x86_64.rpm](https://dl.min.io/aistor/minio/release/linux-amd64/minio-20260317212516.0.0-1.x86_64.rpm)   |\n| RPM    | arm64        | [minio-20260317212516.0.0-1.aarch64.rpm](https://dl.min.io/aistor/minio/release/linux-arm64/minio-20260317212516.0.0-1.aarch64.rpm) |\n\n### Container Images\n\n```bash\n# Standard\ndocker pull quay.io/minio/aistor/minio:RELEASE.2026-03-17T21-25-16Z\npodman pull quay.io/minio/aistor/minio:RELEASE.2026-03-17T21-25-16Z\n\n# FIPS\ndocker pull quay.io/minio/aistor/minio:RELEASE.2026-03-17T21-25-16Z.fips\npodman pull quay.io/minio/aistor/minio:RELEASE.2026-03-17T21-25-16Z.fips\n```\n\n### Homebrew (macOS)\n\n```bash\nbrew install minio/aistor/minio\n```\n\n### Workarounds\n\n- [Users of the open-source `minio/minio` project should upgrade to MinIO AIStor `RELEASE.2026-03-17T21-25-16Z` or later.](https://docs.min.io/enterprise/aistor-object-store/upgrade-aistor-server/community-edition/)\n- As a workaround, ensure that the OIDC `ClientSecret` is treated as a highly sensitive credential and is not exposed to untrusted parties.",
  "id": "GHSA-5cx5-wh4m-82fh",
  "modified": "2026-03-27T21:57:21Z",
  "published": "2026-03-19T17:56:37Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/minio/minio/security/advisories/GHSA-5cx5-wh4m-82fh"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-33322"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/minio/minio"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "MinIO has JWT Algorithm Confusion in OIDC Authentication"
}

GHSA-5F2C-VHF8-FRF8

Vulnerability from github – Published: 2022-05-17 04:44 – Updated: 2022-05-17 04:44
VLAI
Details

Session fixation vulnerability in Foreman before 1.4.2 allows remote attackers to hijack web sessions via the session id cookie.

Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2014-0090"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-287"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2014-05-08T14:29:00Z",
    "severity": "MODERATE"
  },
  "details": "Session fixation vulnerability in Foreman before 1.4.2 allows remote attackers to hijack web sessions via the session id cookie.",
  "id": "GHSA-5f2c-vhf8-frf8",
  "modified": "2022-05-17T04:44:31Z",
  "published": "2022-05-17T04:44:31Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2014-0090"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/errata/RHEA-2014:1175"
    },
    {
      "type": "WEB",
      "url": "https://access.redhat.com/security/cve/CVE-2014-0090"
    },
    {
      "type": "WEB",
      "url": "https://bugzilla.redhat.com/show_bug.cgi?id=1072151"
    },
    {
      "type": "WEB",
      "url": "http://projects.theforeman.org/issues/4457"
    },
    {
      "type": "WEB",
      "url": "http://theforeman.org/security.html"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

GHSA-5F5V-X476-84XC

Vulnerability from github – Published: 2022-05-17 04:04 – Updated: 2022-05-17 04:04
VLAI
Details

The default configuration of Cisco Small Business IP phones SPA 300 7.5.5 and SPA 500 7.5.5 does not properly support authentication, which allows remote attackers to read audio-stream data or originate telephone calls via a crafted XML request, aka Bug ID CSCuo52482.

Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2015-0670"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-287"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2015-03-21T01:59:00Z",
    "severity": "MODERATE"
  },
  "details": "The default configuration of Cisco Small Business IP phones SPA 300 7.5.5 and SPA 500 7.5.5 does not properly support authentication, which allows remote attackers to read audio-stream data or originate telephone calls via a crafted XML request, aka Bug ID CSCuo52482.",
  "id": "GHSA-5f5v-x476-84xc",
  "modified": "2022-05-17T04:04:30Z",
  "published": "2022-05-17T04:04:30Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2015-0670"
    },
    {
      "type": "WEB",
      "url": "http://tools.cisco.com/security/center/viewAlert.x?alertId=37946"
    },
    {
      "type": "WEB",
      "url": "http://www.securitytracker.com/id/1031969"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

GHSA-5F64-WWGV-QHFQ

Vulnerability from github – Published: 2022-05-02 00:00 – Updated: 2022-05-02 00:00
VLAI
Details

Session fixation vulnerability in phpFreeChat 1.1 allows remote authenticated users to hijack web sessions by setting the session_id parameter to match the victim's nickid parameter.

Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2008-3428"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-287"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2008-07-31T22:41:00Z",
    "severity": "MODERATE"
  },
  "details": "Session fixation vulnerability in phpFreeChat 1.1 allows remote authenticated users to hijack web sessions by setting the session_id parameter to match the victim\u0027s nickid parameter.",
  "id": "GHSA-5f64-wwgv-qhfq",
  "modified": "2022-05-02T00:00:06Z",
  "published": "2022-05-02T00:00:06Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2008-3428"
    },
    {
      "type": "WEB",
      "url": "https://exchange.xforce.ibmcloud.com/vulnerabilities/44116"
    },
    {
      "type": "WEB",
      "url": "http://secunia.com/advisories/31283"
    },
    {
      "type": "WEB",
      "url": "http://www.phpfreechat.net/changelog/1.2"
    },
    {
      "type": "WEB",
      "url": "http://www.securityfocus.com/bid/30462"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

GHSA-5FCQ-R7M3-PXF5

Vulnerability from github – Published: 2022-04-30 18:10 – Updated: 2025-04-03 03:33
VLAI
Details

In some cases, Service Pack 4 for Windows NT 4.0 can allow access to network shares using a blank password, through a problem with a null NT hash value.

Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-1999-0366"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-287"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "1999-02-08T05:00:00Z",
    "severity": "HIGH"
  },
  "details": "In some cases, Service Pack 4 for Windows NT 4.0 can allow access to network shares using a blank password, through a problem with a null NT hash value.",
  "id": "GHSA-5fcq-r7m3-pxf5",
  "modified": "2025-04-03T03:33:34Z",
  "published": "2022-04-30T18:10:27Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-1999-0366"
    },
    {
      "type": "WEB",
      "url": "https://docs.microsoft.com/en-us/security-updates/securitybulletins/1999/ms99-004"
    },
    {
      "type": "WEB",
      "url": "http://support.microsoft.com/default.aspx?scid=kb%3B%5BLN%5D%3BQ214840"
    },
    {
      "type": "WEB",
      "url": "http://support.microsoft.com/default.aspx?scid=kb;[LN];Q214840"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

GHSA-5FFH-V4JR-F65H

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

Improper authentication in Azure Local Disconnected Operations allows an unauthorized attacker to elevate privileges over a network.

Severity
10.0 (Critical)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2026-42822"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-287"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-05-18T18:17:34Z",
    "severity": "CRITICAL"
  },
  "details": "Improper authentication in Azure Local Disconnected Operations allows an unauthorized attacker to elevate privileges over a network.",
  "id": "GHSA-5ffh-v4jr-f65h",
  "modified": "2026-05-18T18:31:30Z",
  "published": "2026-05-18T18:31:30Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-42822"
    },
    {
      "type": "WEB",
      "url": "https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-42822"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-5FFJ-X2FF-2JP7

Vulnerability from github – Published: 2022-05-17 04:16 – Updated: 2022-05-17 04:16
VLAI
Details

The rsync daemon in F5 BIG-IP 11.6 before 11.6.0, 11.5.1 before HF3, 11.5.0 before HF4, 11.4.1 before HF4, 11.4.0 before HF7, 11.3.0 before HF9, and 11.2.1 before HF11 and Enterprise Manager 3.x before 3.1.1 HF2, when configured in failover mode, does not require authentication, which allows remote attackers to read or write to arbitrary files via a cmi request to the ConfigSync IP address.

Show details on source website
To clipboard 

{
  "affected": [],
  "aliases": [
    "CVE-2014-2927"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-287"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2014-10-15T14:55:00Z",
    "severity": "HIGH"
  },
  "details": "The rsync daemon in F5 BIG-IP 11.6 before 11.6.0, 11.5.1 before HF3, 11.5.0 before HF4, 11.4.1 before HF4, 11.4.0 before HF7, 11.3.0 before HF9, and 11.2.1 before HF11 and Enterprise Manager 3.x before 3.1.1 HF2, when configured in failover mode, does not require authentication, which allows remote attackers to read or write to arbitrary files via a cmi request to the ConfigSync IP address.",
  "id": "GHSA-5ffj-x2ff-2jp7",
  "modified": "2022-05-17T04:16:58Z",
  "published": "2022-05-17T04:16:58Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2014-2927"
    },
    {
      "type": "WEB",
      "url": "https://support.f5.com/kb/en-us/solutions/public/15000/200/sol15236.html"
    },
    {
      "type": "WEB",
      "url": "http://www.exploit-db.com/exploits/34465"
    },
    {
      "type": "WEB",
      "url": "http://www.security-assessment.com/files/documents/advisory/F5_Unauthenticated_rsync_access_to_Remote_Root_Code_Execution.pdf"
    }
  ],
  "schema_version": "1.4.0",
  "severity": []
}

GHSA-5FG6-WRQ4-W5GH

Vulnerability from github – Published: 2026-03-12 14:47 – Updated: 2026-03-12 14:47
VLAI
Summary
AdGuard Home: HTTP/2 Cleartext (h2c) Upgrade Authentication Bypass
Details

VULNERABILITY: HTTP/2 Cleartext (h2c) Upgrade Authentication Bypass

Severity:  CRITICAL CVSS 3.1:  9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) CWE:       CWE-287 (Improper Authentication) Component: internal/home/web.go Affected:  AdGuardHome (tested on v0.107.72)

Summary

An unauthenticated remote attacker can bypass all authentication in AdGuardHome by sending an HTTP/1.1 request that requests an upgrade to HTTP/2 cleartext (h2c). Once the upgrade is accepted, the resulting HTTP/2 connection is handled by the inner mux, which has no authentication middleware attached. All subsequent HTTP/2 requests on that connection are processed as fully authenticated, regardless of whether any credentials were provided.

Root Cause

In internal/home/web.go (approximately lines 268-283), the HTTP server is constructed as follows:     hdlr := h2c.NewHandler(         withMiddlewares(web.conf.mux, limitRequestBody),  // no auth         &http2.Server{},     )     web.httpServer = &http.Server{         Handler: web.auth.middleware().Wrap(hdlr),        // auth here     }

The authentication middleware wraps the h2c handler at the outer layer. When an h2c upgrade request arrives, the h2c library hijacks the TCP connection and calls http2.ServeConn with Handler set to the inner mux, which was stored at h2c.NewHandler creation time. The authentication middleware is never consulted for any request sent over the resulting HTTP/2 connection. The upgrade request itself passes through because it targets a public path (such as /control/login), which is whitelisted by isPublicResource() in internal/home/authhttp.go. After the upgrade, the attacker can reach any administrative endpoint.

Proof of Concept

The PoC script (https://gist.github.com/mandreko/f742d244dfa452e8d00cc5736cf8d629) demonstrates the bypass using a raw TCP connection with HTTP/2 framing. No credentials are provided at any point.

Steps:   1. Open TCP connection to AdGuardHome (default port 3000).   2. Send HTTP/1.1 GET /control/login with headers:        Upgrade: h2c        Connection: Upgrade, HTTP2-Settings        HTTP2-Settings: AAMAAABkAAQAAP__   3. Server responds: 101 Switching Protocols.   4. Complete HTTP/2 handshake (client preface + SETTINGS exchange).   5. Send HTTP/2 HEADERS frame requesting GET /control/status on stream 3.   6. Server responds: HTTP 200 with full JSON status payload.

Sample output (no username or password supplied):     python3 poc_h2c_auth_bypass.py 192.168.1.15 80 --hijack-dns 8.8.8.8     ====================================================================     AdGuardHome -- h2c Authentication Bypass PoC     CWE-287: Full API access without credentials     ====================================================================     Target  : http://192.168.1.15:80     Upgrade : /control/login  (whitelisted public path)

[*] Connecting and performing h2c upgrade ...     [+] Bypass established -- authentication is not enforced

[*] GET /control/status     [+] Version      : v0.107.72     [+] DNS addresses: ['127.0.0.1', '::1', '192.168.1.15', 'fd64:b28c:45d2:4b5e:d35c:7660:e1b:92', 'fe80::ba65:3afa:617f:f077%eth0']     [+] HTTP port    : 80     [+] Protection   : ON

[*] GET /control/querylog  (DNS query history)     [+] 10 recent entries:         2026-03-09T20:42:15  docker.home.andreko.net                   192.168.1.232         2026-03-09T20:42:00  docker.home.andreko.net                   192.168.1.232         2026-03-09T20:41:45  docker.home.andreko.net                   192.168.1.232         2026-03-09T20:41:30  docker.home.andreko.net                   192.168.1.232         2026-03-09T20:41:12  docker.home.andreko.net                   192.168.1.232

[*] GET /control/dhcp/status  (network device inventory)     [+] Dynamic leases : 0     [+] Static leases  : 0

[*] POST /control/dns_config  (DNS -> 8.8.8.8)     [+] Upstream DNS changed to 8.8.8.8     [+] All DNS queries now route through attacker-controlled server

The bypass gives full administrative API access, including:   - Reading and modifying DNS configuration   - Adding malicious filter lists   - Disabling protection   - Changing the admin password   - Hijacking DNS resolution for all clients on the network

Remediation

Move the authentication middleware inside the h2c handler so it applies to all connections regardless of protocol:     authedMux := web.auth.middleware().Wrap(         withMiddlewares(web.conf.mux, limitRequestBody),     )     hdlr := h2c.NewHandler(authedMux, &http2.Server{})     web.httpServer = &http.Server{         Handler: hdlr,     }

Alternatively, if h2c support is not required, removing h2c.NewHandler entirely would eliminate the attack surface. HTTP/2 over TLS (h2) is not affected by this vulnerability.

Severity
9.8 (Critical)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Show details on source website
To clipboard 

{
  "affected": [
    {
      "package": {
        "ecosystem": "Go",
        "name": "github.com/AdguardTeam/AdGuardHome"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.107.73"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-32136"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-287"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-03-12T14:47:48Z",
    "nvd_published_at": "2026-03-11T22:16:33Z",
    "severity": "CRITICAL"
  },
  "details": "VULNERABILITY: HTTP/2 Cleartext (h2c) Upgrade Authentication Bypass\n========================================================================\nSeverity: \u00a0CRITICAL\nCVSS 3.1: \u00a09.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H)\nCWE: \u00a0 \u00a0 \u00a0 CWE-287 (Improper Authentication)\nComponent: internal/home/web.go\nAffected: \u00a0AdGuardHome (tested on v0.107.72)\n\n------------------------------------------------------------------------\nSummary\n------------------------------------------------------------------------\n\nAn unauthenticated remote attacker can bypass all authentication in AdGuardHome by sending an HTTP/1.1 request that requests an upgrade to HTTP/2 cleartext (h2c). Once the upgrade is accepted, the resulting HTTP/2 connection is handled by the inner mux, which has no authentication middleware attached. All subsequent HTTP/2 requests on that connection are processed as fully authenticated, regardless of whether any credentials were provided.\n\n------------------------------------------------------------------------\nRoot Cause\n------------------------------------------------------------------------\n\nIn internal/home/web.go (approximately lines 268-283), the HTTP server is constructed as follows:\n\u00a0 \u00a0 hdlr := h2c.NewHandler(\n\u00a0 \u00a0 \u00a0 \u00a0 withMiddlewares(web.conf.mux, limitRequestBody), \u00a0// no auth\n\u00a0 \u00a0 \u00a0 \u00a0 \u0026http2.Server{},\n\u00a0 \u00a0 )\n\u00a0 \u00a0 web.httpServer = \u0026http.Server{\n\u00a0 \u00a0 \u00a0 \u00a0 Handler: web.auth.middleware().Wrap(hdlr), \u00a0 \u00a0 \u00a0 \u00a0// auth here\n\u00a0 \u00a0 }\n\nThe authentication middleware wraps the h2c handler at the outer layer. When an h2c upgrade request arrives, the h2c library hijacks the TCP connection and calls http2.ServeConn with Handler set to the inner mux, which was stored at h2c.NewHandler creation time. The authentication middleware is never consulted for any request sent over the resulting HTTP/2 connection. The upgrade request itself passes through because it targets a public path (such as /control/login), which is whitelisted by isPublicResource() in internal/home/authhttp.go. After the upgrade, the attacker can reach any administrative endpoint.\n\n------------------------------------------------------------------------\nProof of Concept\n------------------------------------------------------------------------\n\nThe PoC script (https://gist.github.com/mandreko/f742d244dfa452e8d00cc5736cf8d629) demonstrates the bypass using a raw TCP connection with HTTP/2 framing. No credentials are provided at any point.\n\nSteps:\n\u00a0 1. Open TCP connection to AdGuardHome (default port 3000).\n\u00a0 2. Send HTTP/1.1 GET /control/login with headers:\n\u00a0 \u00a0 \u00a0 \u00a0Upgrade: h2c\n\u00a0 \u00a0 \u00a0 \u00a0Connection: Upgrade, HTTP2-Settings\n\u00a0 \u00a0 \u00a0 \u00a0HTTP2-Settings: AAMAAABkAAQAAP__\n\u00a0 3. Server responds: 101 Switching Protocols.\n\u00a0 4. Complete HTTP/2 handshake (client preface + SETTINGS exchange).\n\u00a0 5. Send HTTP/2 HEADERS frame requesting GET /control/status on stream 3.\n\u00a0 6. Server responds: HTTP 200 with full JSON status payload.\n\nSample output (no username or password supplied):\n\u00a0 \u00a0 python3 poc_h2c_auth_bypass.py 192.168.1.15 80 --hijack-dns 8.8.8.8\n\u00a0 \u00a0 ====================================================================\n\u00a0 \u00a0 AdGuardHome -- h2c Authentication Bypass PoC\n\u00a0 \u00a0 CWE-287: Full API access without credentials\n\u00a0 \u00a0 ====================================================================\n\u00a0 \u00a0 Target \u00a0: [http://192.168.1.15:80](http://192.168.1.15/)\n\u00a0 \u00a0 Upgrade : /control/login \u00a0(whitelisted public path)\n\n\u00a0 \u00a0 [*] Connecting and performing h2c upgrade ...\n\u00a0 \u00a0 [+] Bypass established -- authentication is not enforced\n\n\u00a0 \u00a0 [*] GET /control/status\n\u00a0 \u00a0 [+] Version \u00a0 \u00a0 \u00a0: v0.107.72\n\u00a0 \u00a0 [+] DNS addresses: [\u0027127.0.0.1\u0027, \u0027::1\u0027, \u0027192.168.1.15\u0027, \u0027fd64:b28c:45d2:4b5e:d35c:7660:e1b:92\u0027, \u0027fe80::ba65:3afa:617f:f077%eth0\u0027]\n\u00a0 \u00a0 [+] HTTP port \u00a0 \u00a0: 80\n\u00a0 \u00a0 [+] Protection \u00a0 : ON\n\n\u00a0 \u00a0 [*] GET /control/querylog \u00a0(DNS query history)\n\u00a0 \u00a0 [+] 10 recent entries:\n\u00a0 \u00a0 \u00a0 \u00a0 2026-03-09T20:42:15 \u00a0[docker.home.andreko.net](http://docker.home.andreko.net/) \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 192.168.1.232\n\u00a0 \u00a0 \u00a0 \u00a0 2026-03-09T20:42:00 \u00a0[docker.home.andreko.net](http://docker.home.andreko.net/) \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 192.168.1.232\n\u00a0 \u00a0 \u00a0 \u00a0 2026-03-09T20:41:45 \u00a0[docker.home.andreko.net](http://docker.home.andreko.net/) \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 192.168.1.232\n\u00a0 \u00a0 \u00a0 \u00a0 2026-03-09T20:41:30 \u00a0[docker.home.andreko.net](http://docker.home.andreko.net/) \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 192.168.1.232\n\u00a0 \u00a0 \u00a0 \u00a0 2026-03-09T20:41:12 \u00a0[docker.home.andreko.net](http://docker.home.andreko.net/) \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 192.168.1.232\n\n\u00a0 \u00a0 [*] GET /control/dhcp/status \u00a0(network device inventory)\n\u00a0 \u00a0 [+] Dynamic leases : 0\n\u00a0 \u00a0 [+] Static leases \u00a0: 0\n\n\u00a0 \u00a0 [*] POST /control/dns_config \u00a0(DNS -\u003e 8.8.8.8)\n\u00a0 \u00a0 [+] Upstream DNS changed to 8.8.8.8\n\u00a0 \u00a0 [+] All DNS queries now route through attacker-controlled server\n\nThe bypass gives full administrative API access, including:\n\u00a0 - Reading and modifying DNS configuration\n\u00a0 - Adding malicious filter lists\n\u00a0 - Disabling protection\n\u00a0 - Changing the admin password\n\u00a0 - Hijacking DNS resolution for all clients on the network\n\n------------------------------------------------------------------------\nRemediation\n------------------------------------------------------------------------\n\nMove the authentication middleware inside the h2c handler so it applies to all connections regardless of protocol:\n\u00a0 \u00a0 authedMux := web.auth.middleware().Wrap(\n\u00a0 \u00a0 \u00a0 \u00a0 withMiddlewares(web.conf.mux, limitRequestBody),\n\u00a0 \u00a0 )\n\u00a0 \u00a0 hdlr := h2c.NewHandler(authedMux, \u0026http2.Server{})\n\u00a0 \u00a0 web.httpServer = \u0026http.Server{\n\u00a0 \u00a0 \u00a0 \u00a0 Handler: hdlr,\n\u00a0 \u00a0 }\n\nAlternatively, if h2c support is not required, removing h2c.NewHandler entirely would eliminate the attack surface. HTTP/2 over TLS (h2) is not affected by this vulnerability.",
  "id": "GHSA-5fg6-wrq4-w5gh",
  "modified": "2026-03-12T14:47:48Z",
  "published": "2026-03-12T14:47:48Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/AdguardTeam/AdGuardHome/security/advisories/GHSA-5fg6-wrq4-w5gh"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-32136"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/AdguardTeam/AdGuardHome"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "AdGuard Home: HTTP/2 Cleartext (h2c) Upgrade Authentication Bypass"
}
Mitigation
Architecture and Design

Strategy: Libraries or Frameworks

Use an authentication framework or library such as the OWASP ESAPI Authentication feature.

CAPEC-114: Authentication Abuse

An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker.

CAPEC-115: Authentication Bypass

An attacker gains access to application, service, or device with the privileges of an authorized or privileged user by evading or circumventing an authentication mechanism. The attacker is therefore able to access protected data without authentication ever having taken place.

CAPEC-151: Identity Spoofing

Identity Spoofing refers to the action of assuming (i.e., taking on) the identity of some other entity (human or non-human) and then using that identity to accomplish a goal. An adversary may craft messages that appear to come from a different principle or use stolen / spoofed authentication credentials.

CAPEC-194: Fake the Source of Data

An adversary takes advantage of improper authentication to provide data or services under a falsified identity. The purpose of using the falsified identity may be to prevent traceability of the provided data or to assume the rights granted to another individual. One of the simplest forms of this attack would be the creation of an email message with a modified "From" field in order to appear that the message was sent from someone other than the actual sender. The root of the attack (in this case the email system) fails to properly authenticate the source and this results in the reader incorrectly performing the instructed action. Results of the attack vary depending on the details of the attack, but common results include privilege escalation, obfuscation of other attacks, and data corruption/manipulation.

CAPEC-22: Exploiting Trust in Client

An attack of this type exploits vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by communicating directly with the server where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.

CAPEC-57: Utilizing REST's Trust in the System Resource to Obtain Sensitive Data

This attack utilizes a REST(REpresentational State Transfer)-style applications' trust in the system resources and environment to obtain sensitive data once SSL is terminated.

CAPEC-593: Session Hijacking

This type of attack involves an adversary that exploits weaknesses in an application's use of sessions in performing authentication. The adversary is able to steal or manipulate an active session and use it to gain unathorized access to the application.

CAPEC-633: Token Impersonation

An adversary exploits a weakness in authentication to create an access token (or equivalent) that impersonates a different entity, and then associates a process/thread to that that impersonated token. This action causes a downstream user to make a decision or take action that is based on the assumed identity, and not the response that blocks the adversary.

CAPEC-650: Upload a Web Shell to a Web Server

By exploiting insufficient permissions, it is possible to upload a web shell to a web server in such a way that it can be executed remotely. This shell can have various capabilities, thereby acting as a "gateway" to the underlying web server. The shell might execute at the higher permission level of the web server, providing the ability the execute malicious code at elevated levels.

CAPEC-94: Adversary in the Middle (AiTM)

An adversary targets the communication between two components (typically client and server), in order to alter or obtain data from transactions. A general approach entails the adversary placing themself within the communication channel between the two components.

← Back to the CWE list