How severe is CVE-2022-38817?

CVE-2022-38817 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-38817?

CVE-2022-38817 affects the following packages: github.com/dapr/dashboard (Go). Ecosystems affected: Go.

How do I fix CVE-2022-38817?

The records we use list no patched version of github.com/dapr/dashboard for CVE-2022-38817. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2022-38817 in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/dapr/dashboard, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-38817 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2022-38817 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-38817, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-38817?

CVE-2022-38817 has an EPSS (Exploit Prediction Scoring System) score of 3.9%, placing it in the 90th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-38817?

CVE-2022-38817 is classified as Missing Authentication (CWE-306). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2022-38817?

A Nuclei detection template exists for CVE-2022-38817, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2022-38817 published, and has it been updated?

CVE-2022-38817 was published on October 3, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹

🐹 Go

Not in CISA KEV

HIGH severity

CVE-2022-38817 — dashboard

HIGH

CVE-2022-38817 is a high-severity (CVSS 7.5) Missing Authentication vulnerability in github.com/dapr/dashboard. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Dapr Dashboard vulnerable to Incorrect Access Control

Also known asGHSA-2w6m-q946-399rGO-2022-1033

Published

Oct 3, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

See advisory

Exploits

1 known

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

3.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs90th percentile — riskier than 90% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐹github.com/dapr/dashboard

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Dapr Dashboard v0.1.0 through v0.10.0 is vulnerable to Incorrect Access Control that allows attackers to obtain sensitive data.

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/dapr/dashboard`	≥ 0.1.0	No fix

Affected Products

1 product · 1 configurations

Application

dapr dashboardlinuxfoundation

≥ 0.1.0 && ≤ 0.10.0

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Dapr Dashboard v0.1.0 through v0.10.0 is vulnerable to Incorrect Access …

github.comNVDOct 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/dapr/dashboard, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of github.com/dapr/dashboard for CVE-2022-38817. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

How to detect CVE-2022-38817

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2022-38817 -u https://target

Template: Dapr Dashboard 0.1.0-0.10.0 - Improper Access Control
Severity: high
Impact: The vulnerability allows unauthorized access to the Dapr Dashboard, potentially leading to unauthorized actions and data exposure.
Remediation: Upgrade Dapr Dashboard to a version that includes the fix for CVE-2022-38817 or apply the necessary patches provided by the vendor.

Template by ProjectDiscovery nuclei-templates (For3stCo1d), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

Dapr Dashboard v0.1.0 through v0.10.0 is vulnerable to Incorrect Access Control that allows attackers to obtain sensitive data.

O3 Security · Impact-Aware SCA

Is CVE-2022-38817 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

7.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CWE Classification

CWE-306Missing Authentication

Weaponization

Timeline

Disclosed

Oct 3, 2022

First exploit

Oct 5, 2022

2 days after disclosure — rapid exploitation

Last updated

Oct 28, 2026

Identifiers

CVE-2022-38817

GHSA-2w6m-q946-399r

GO-2022-1033

References

Advisorygithub.com · CVE 2022 38817.json Advisorynvd.nist.gov · CVE 2022 38817 Reportgithub.com Packagegithub.com · dashboard

Related vulnerabilities

This CVE is high severity; 5 of 8 other CVEs with CWE-306 are rated as high or higher (top: critical).

GHSA-m3qr-fvp4-78xjCVE-2026-62264CVE-2026-114126CVE-2026-112949CVE-2026-113648CVE-2026-105192CVE-2026-84313CVE-2026-102748Browse all CWE-306

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2022-38817 — dashboard

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

How to detect CVE-2022-38817

Frequently Asked Questions

Is CVE-2022-38817 in your dependencies?