Skip to content

Commit 0be305b

Browse files
advisory-database[bot]advisory-database[bot]
committed
Publish Advisories
GHSA-3458-r943-hmx4 GHSA-99hj-44vg-hfcp
1 parent f10eed9 commit 0be305b

2 files changed

Lines changed: 114 additions & 0 deletions

File tree

‎advisories/github-reviewed/2026/03/GHSA-3458-r943-hmx4/GHSA-3458-r943-hmx4.json‎

Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-3458-r943-hmx4",
4+
"modified": "2026-03-27T18:17:20Z",
5+
"published": "2026-03-27T18:17:09Z",
6+
"aliases": [
7+
"CVE-2026-26060"
8+
],
9+
"summary": "Fleet: Password reset tokens remain valid after password change for 24 hours",
10+
"details": "### Summary\n\nA vulnerability in Fleet’s password management logic could allow previously issued password reset tokens to remain valid after a user changes their password. As a result, a stale password reset token could be reused to reset the account password even after a defensive password change.\n\n### Impact\n\nIf an attacker had prior access to a valid password reset token, they could reuse that token within its validity window to reset the user’s password after the user has already changed it. This could result in temporary account takeover.\n\nExploitation requires prior compromise of a password reset token and is further constrained by the token’s 24-hour expiration period. The issue does not allow discovery of reset tokens, does not bypass authentication on its own, and does not affect accounts without an existing valid reset token.\n\n### Workarounds\n\nUntil patched, users who believe a password reset token may have been exposed should wait for the token to expire before reusing the account, or contact a Fleet administrator to invalidate active sessions.\n\n### For more information\n\nIf there are any questions or comments about this advisory:\n\nEmail Fleet at [security@fleetdm.com](mailto:security@fleetdm.com) \nJoin #fleet in [osquery Slack](https://join.slack.com/t/osquery/shared_invite/zt-h29zm0gk-s2DBtGUTW4CFel0f0IjTEw)\n\n### Credits\n\nFleet thanks @fuzzztf for responsibly reporting this issue.",
11+
"severity": [
12+
{
13+
"type": "CVSS_V4",
14+
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N"
15+
}
16+
],
17+
"affected": [
18+
{
19+
"package": {
20+
"ecosystem": "Go",
21+
"name": "github.com/fleetdm/fleet/v4"
22+
},
23+
"ranges": [
24+
{
25+
"type": "ECOSYSTEM",
26+
"events": [
27+
{
28+
"introduced": "0"
29+
},
30+
{
31+
"fixed": "4.43.5-0.20260113202849-bbc1aef2987d"
32+
}
33+
]
34+
}
35+
]
36+
}
37+
],
38+
"references": [
39+
{
40+
"type": "WEB",
41+
"url": "https://github.com/fleetdm/fleet/security/advisories/GHSA-3458-r943-hmx4"
42+
},
43+
{
44+
"type": "PACKAGE",
45+
"url": "https://github.com/fleetdm/fleet"
46+
}
47+
],
48+
"database_specific": {
49+
"cwe_ids": [
50+
"CWE-613"
51+
],
52+
"severity": "MODERATE",
53+
"github_reviewed": true,
54+
"github_reviewed_at": "2026-03-27T18:17:09Z",
55+
"nvd_published_at": null
56+
}
57+
}

‎advisories/github-reviewed/2026/03/GHSA-99hj-44vg-hfcp/GHSA-99hj-44vg-hfcp.json‎

Lines changed: 57 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,57 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-99hj-44vg-hfcp",
4+
"modified": "2026-03-27T18:17:42Z",
5+
"published": "2026-03-27T18:17:42Z",
6+
"aliases": [
7+
"CVE-2026-26061"
8+
],
9+
"summary": "Fleet's unbounded request body read allows remote Denial of Service",
10+
"details": "### Summary\n\nFleet contained multiple unauthenticated HTTP endpoints that read request bodies without enforcing a size limit. An unauthenticated attacker could exploit this behavior by sending large or repeated HTTP payloads, causing excessive memory allocation and resulting in a denial-of-service (DoS) condition.\n\n### Impact\n\nAn unauthenticated attacker could cause the Fleet server process to exhaust available memory and restart by sending oversized or repeated HTTP requests to affected endpoints.\n\nThis vulnerability impacts **availability only**. There is:\n\n- No exposure of sensitive data\n- No authentication bypass\n- No privilege escalation\n- No integrity impact\n\n### Workarounds\n\nIf upgrading immediately is not possible, the following mitigations can reduce exposure:\n\n- Apply request body size limits at a reverse proxy or load balancer (e.g., NGINX, Envoy).\n- Restrict network access to endpoints to known IP ranges where feasible.\n- Monitor memory usage and restart frequency for abnormal patterns.\n\n### For More Information\n\nIf there are any questions or concerns about this advisory, please contact us at:\n\nEmail Fleet at [security@fleetdm.com](mailto:security@fleetdm.com)\n\n### Credits\n\nFleet thanks @fuzzztf for responsibly reporting this issue.",
11+
"severity": [
12+
{
13+
"type": "CVSS_V4",
14+
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N"
15+
}
16+
],
17+
"affected": [
18+
{
19+
"package": {
20+
"ecosystem": "Go",
21+
"name": "github.com/fleetdm/fleet/v4"
22+
},
23+
"ranges": [
24+
{
25+
"type": "ECOSYSTEM",
26+
"events": [
27+
{
28+
"introduced": "0"
29+
},
30+
{
31+
"fixed": "4.43.5-0.20260113202849-bbc1aef2987d"
32+
}
33+
]
34+
}
35+
]
36+
}
37+
],
38+
"references": [
39+
{
40+
"type": "WEB",
41+
"url": "https://github.com/fleetdm/fleet/security/advisories/GHSA-99hj-44vg-hfcp"
42+
},
43+
{
44+
"type": "PACKAGE",
45+
"url": "https://github.com/fleetdm/fleet"
46+
}
47+
],
48+
"database_specific": {
49+
"cwe_ids": [
50+
"CWE-770"
51+
],
52+
"severity": "HIGH",
53+
"github_reviewed": true,
54+
"github_reviewed_at": "2026-03-27T18:17:42Z",
55+
"nvd_published_at": null
56+
}
57+
}

0 commit comments

Comments
 (0)