Skip to content

Commit 0dd7696

Browse files
advisory-database[bot]advisory-database[bot]
committed
Publish Advisories
GHSA-h8wq-7xc4-p3qx GHSA-29x4-r6jv-ff4w GHSA-452v-w3gx-72wg GHSA-8m29-fpq5-89jj GHSA-9j88-vvj5-vhgr
1 parent aef5bed commit 0dd7696

File tree

5 files changed

+315
-4
lines changed

5 files changed

+315
-4
lines changed

advisories/unreviewed/2026/03/GHSA-h8wq-7xc4-p3qx/GHSA-h8wq-7xc4-p3qx.json renamed to advisories/github-reviewed/2026/03/GHSA-h8wq-7xc4-p3qx/GHSA-h8wq-7xc4-p3qx.json

Lines changed: 37 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,57 @@
11
{
22
"schema_version": "1.4.0",
33
"id": "GHSA-h8wq-7xc4-p3qx",
4-
"modified": "2026-03-09T21:31:38Z",
4+
"modified": "2026-04-18T01:14:15Z",
55
"published": "2026-03-09T21:31:38Z",
66
"aliases": [
77
"CVE-2026-0846"
88
],
9+
"summary": "NLTK has Arbitrary File Read via Absolute Path Input in nltk.util.filestring()",
910
"details": "A vulnerability in the `filestring()` function of the `nltk.util` module in nltk version 3.9.2 allows arbitrary file read due to improper validation of input paths. The function directly opens files specified by user input without sanitization, enabling attackers to access sensitive system files by providing absolute paths or traversal paths. This vulnerability can be exploited locally or remotely, particularly in scenarios where the function is used in web APIs or other interfaces that accept user-supplied input.",
1011
"severity": [
1112
{
1213
"type": "CVSS_V3",
1314
"score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L"
1415
}
1516
],
16-
"affected": [],
17+
"affected": [
18+
{
19+
"package": {
20+
"ecosystem": "PyPI",
21+
"name": "nltk"
22+
},
23+
"ranges": [
24+
{
25+
"type": "ECOSYSTEM",
26+
"events": [
27+
{
28+
"introduced": "0"
29+
},
30+
{
31+
"fixed": "3.9.3"
32+
}
33+
]
34+
}
35+
]
36+
}
37+
],
1738
"references": [
1839
{
1940
"type": "ADVISORY",
2041
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-0846"
2142
},
43+
{
44+
"type": "WEB",
45+
"url": "https://github.com/nltk/nltk/pull/3485"
46+
},
47+
{
48+
"type": "WEB",
49+
"url": "https://github.com/nltk/nltk/commit/b2e1164bf89277f79b65406c829b99fb20ca1974"
50+
},
51+
{
52+
"type": "PACKAGE",
53+
"url": "https://github.com/nltk/nltk"
54+
},
2255
{
2356
"type": "WEB",
2457
"url": "https://huntr.com/bounties/007b84f8-418e-4300-99d0-bf504c2f97eb"
@@ -29,8 +62,8 @@
2962
"CWE-36"
3063
],
3164
"severity": "HIGH",
32-
"github_reviewed": false,
33-
"github_reviewed_at": null,
65+
"github_reviewed": true,
66+
"github_reviewed_at": "2026-04-18T01:14:15Z",
3467
"nvd_published_at": "2026-03-09T20:16:05Z"
3568
}
3669
}

‎advisories/github-reviewed/2026/04/GHSA-29x4-r6jv-ff4w/GHSA-29x4-r6jv-ff4w.json‎

Lines changed: 75 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,75 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-29x4-r6jv-ff4w",
4+
"modified": "2026-04-18T01:15:10Z",
5+
"published": "2026-04-18T01:15:10Z",
6+
"aliases": [],
7+
"summary": "Zebra Vulnerable to Denial of Service via Interrupted JSON-RPC Requests from Authenticated Clients",
8+
"details": "A vulnerability in Zebra's JSON-RPC HTTP middleware allows an authenticated RPC client to cause a Zebra node to crash by disconnecting before the request body is fully received. The node treats the failure to read the HTTP request body as an unrecoverable error and aborts the process instead of returning an error response.\n\n## Severity\n**Moderate** - This is a Denial of Service (DoS) that requires a client capable of passing Zebra's cookie authentication, which is enabled by default.\n\n## Affected Versions\n- `zebrad`: versions from **2.2.0** up to (but not including) **4.3.1**\n- `zebra-rpc`: versions from **1.0.0-beta.45** up to (but not including) **6.0.2**\n\n## Description\n\nZebra's JSON-RPC HTTP middleware treated a failure to read the incoming HTTP request body as an unrecoverable error, aborting the process rather than returning an error response. A client that disconnected after sending only part of a request body, for example, by resetting the TCP connection mid-transfer, was sufficient to trigger the crash. The vulnerability could be exploited only by authenticated RPC clients. Nodes running the shipped defaults, with RPC bound to localhost and cookie authentication on, were not vulnerable.\n\n## Impact\n**Denial of Service**\n* **Attack Vector:** Network, authenticated (requires a valid RPC cookie when cookie authentication is enabled).\n* **Effect:** Immediate crash of the Zebra node.\n* **Scope:** Any node whose RPC interface is reachable by a client with valid credentials, or any node with cookie authentication disabled and an exposed RPC interface.\n\n## Fixed Versions\nThis issue is fixed in **Zebra 4.3.1** (crate `zebra-rpc` 6.0.2).\n\nThe fix propagates failures to read the HTTP request body as ordinary error responses, so Zebra now rejects truncated or interrupted requests rather than crashing.\n\n## Mitigation\nUsers should upgrade to **Zebra 4.3.1** or later.\n\nIf an immediate upgrade is not possible, users should ensure their RPC port is not exposed to untrusted networks and that cookie authentication remains enabled (the default).\n\n## References\n* [Zebra 4.3.1 Release Announcement](https://zfnd.org/)\n\n## Credits\nThanks to [shieldedonly](https://github.com/shieldedonly) who discovered this issue and reported it via our coordinated disclosure process.",
9+
"severity": [
10+
{
11+
"type": "CVSS_V4",
12+
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H"
13+
}
14+
],
15+
"affected": [
16+
{
17+
"package": {
18+
"ecosystem": "crates.io",
19+
"name": "zebra-rpc"
20+
},
21+
"ranges": [
22+
{
23+
"type": "ECOSYSTEM",
24+
"events": [
25+
{
26+
"introduced": "1.0.0-beta.45"
27+
},
28+
{
29+
"fixed": "6.0.2"
30+
}
31+
]
32+
}
33+
]
34+
},
35+
{
36+
"package": {
37+
"ecosystem": "crates.io",
38+
"name": "zebrad"
39+
},
40+
"ranges": [
41+
{
42+
"type": "ECOSYSTEM",
43+
"events": [
44+
{
45+
"introduced": "2.2.0"
46+
},
47+
{
48+
"fixed": "4.3.1"
49+
}
50+
]
51+
}
52+
]
53+
}
54+
],
55+
"references": [
56+
{
57+
"type": "WEB",
58+
"url": "https://github.com/ZcashFoundation/zebra/security/advisories/GHSA-29x4-r6jv-ff4w"
59+
},
60+
{
61+
"type": "PACKAGE",
62+
"url": "https://github.com/ZcashFoundation/zebra"
63+
}
64+
],
65+
"database_specific": {
66+
"cwe_ids": [
67+
"CWE-248",
68+
"CWE-617"
69+
],
70+
"severity": "MODERATE",
71+
"github_reviewed": true,
72+
"github_reviewed_at": "2026-04-18T01:15:10Z",
73+
"nvd_published_at": null
74+
}
75+
}

‎advisories/github-reviewed/2026/04/GHSA-452v-w3gx-72wg/GHSA-452v-w3gx-72wg.json‎

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-452v-w3gx-72wg",
4+
"modified": "2026-04-18T01:14:57Z",
5+
"published": "2026-04-18T01:14:57Z",
6+
"aliases": [],
7+
"summary": "Zebra has rk Identity Point Panic in Transaction Verification",
8+
"details": "# rk Identity Point Panic in Transaction Verification\n\n## Summary\n\nOrchard transactions contain a `rk` field which is a randomized validating key and also an elliptic curve point. The Zcash specification allows the field to be the identity (a \"zero\" value), however, the `orchard` crate which is used to verify Orchard proofs would panic when fed a `rk` with the identity value. Thus an attacker could send a crafted transaction that would make a Zebra node crash.\n\n## Severity\n\n**Critical** - This is a Denial of Service Vulnerability that could allow an attacker to crash Zebra nodes.\n\n## Affected Versions\n\nAll Zebra versions prior to **version 4.3.1**.\n\n## Description\n\nThe vulnerability exists in the `circuits.rs` file of the `orchard` crate; it attempts to get the coordinates of the `rk` value and calls `unwrap()` on the results, which causes a panic if `rk` is the identity.\n\nZebra parses `rk` as a byte vector; it creates an Orchard \"bundle\" using the `orchard` crate and then calls the same crate to verify it, triggering the panic.\n\nAn attacker could exploit this by:\n1. Creating a transaction with a identity `rk`\n2. Submitting it to a Zebra node, making it crash\n\n## Impact\n\n**Denial of Service**\n\n* **Attack Vector:** Network.\n* **Effect:** Node crash.\n* **Scope:** Any impacted Zebra node.\n\n## Fixed Versions\n\nThis issue is fixed in **Zebra 4.3.1**. \n\nThe fix was agreed with `zcashd` developers (which has the same issue) to not allow the identity `rk` anymore and change the specification as such. Zebra now does this when parsing a transaction. This was deemed easier than fixing the issue in `orchard`, which would make the bug public before the nodes could be patched.\n\n## Mitigation\n\nUsers should upgrade to **Zebra 4.3.1** or later immediately. \n\nThere are no known workarounds for this issue. Immediate upgrade is the only way to ensure the node remains not vulnerable to denial of service.\n\n## Credits\n\nThanks to Alex “Scalar” Sol for finding and reporting the issue.",
9+
"severity": [
10+
{
11+
"type": "CVSS_V4",
12+
"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:H"
13+
}
14+
],
15+
"affected": [
16+
{
17+
"package": {
18+
"ecosystem": "crates.io",
19+
"name": "zebrad"
20+
},
21+
"ranges": [
22+
{
23+
"type": "ECOSYSTEM",
24+
"events": [
25+
{
26+
"introduced": "0"
27+
},
28+
{
29+
"fixed": "4.3.1"
30+
}
31+
]
32+
}
33+
]
34+
},
35+
{
36+
"package": {
37+
"ecosystem": "crates.io",
38+
"name": "zebra-chain"
39+
},
40+
"ranges": [
41+
{
42+
"type": "ECOSYSTEM",
43+
"events": [
44+
{
45+
"introduced": "0"
46+
},
47+
{
48+
"fixed": "6.0.2"
49+
}
50+
]
51+
}
52+
]
53+
}
54+
],
55+
"references": [
56+
{
57+
"type": "WEB",
58+
"url": "https://github.com/ZcashFoundation/zebra/security/advisories/GHSA-452v-w3gx-72wg"
59+
},
60+
{
61+
"type": "PACKAGE",
62+
"url": "https://github.com/ZcashFoundation/zebra"
63+
}
64+
],
65+
"database_specific": {
66+
"cwe_ids": [
67+
"CWE-617"
68+
],
69+
"severity": "CRITICAL",
70+
"github_reviewed": true,
71+
"github_reviewed_at": "2026-04-18T01:14:57Z",
72+
"nvd_published_at": null
73+
}
74+
}

‎advisories/github-reviewed/2026/04/GHSA-8m29-fpq5-89jj/GHSA-8m29-fpq5-89jj.json‎

Lines changed: 74 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,74 @@
1+
{
2+
"schema_version": "1.4.0",
3+
"id": "GHSA-8m29-fpq5-89jj",
4+
"modified": "2026-04-18T01:15:24Z",
5+
"published": "2026-04-18T01:15:24Z",
6+
"aliases": [],
7+
"summary": "Zebra Vulnerable to Consensus Divergence in Transparent Sighash Hash-Type Handling",
8+
"details": "# Consensus Divergence in Transparent Sighash Hash-Type Handling\n\n## Summary\n\nAfter a refactoring, Zebra failed to validate a consensus rule that restricted the possible values of sighash hash types for V5 transactions which were enabled in the NU5 network upgrade. Zebra nodes could thus accept and eventually mine a block that would be considered invalid by zcashd nodes, creating a consensus split between Zebra and zcashd nodes.\n\nIn a similar vein, for V4 transactions, Zebra mistakenly used the \"canonical\" hash type when computing the sighash while zcashd (correctly per the spec) uses the raw value, which could also crate a consensus split.\n\n## Severity\n\n**Critical** - This is a Consensus Vulnerability that could allow a malicious party to induce network partitioning, service disruption, and potential double-spend attacks against affected nodes.\n\nNote that the impact is currently alleviated by the fact that currently most miners run `zcashd`.\n\n## Affected Versions\n\nAll Zebra versions prior to version 4.3.1. (Some older versions are not impacted but are no longer supported by the network.)\n\n## Description\n\nVerification of transparent transactions inherits the Bitcoin Script verification code in C++. Since it is consensus-critical, this code was called from Zebra through foreign function interface (FFI). That interface was clunky because it required parsing the whole transaction in C++ code, which would then pull Rust libraries which could get in conflict with Zebra code. A refactoring was done so that only the verification itself was done in C++, and the rest done by Rust code, using a callback. However, in this refactoring, it was not noticed that a particular consensus rule - only accepting known hash types in transparent transaction signatures - was being enforced in C++ code and thus had to be enforced by the Rust caller.\n\nAn attacker could exploit this by:\n\n- Submitting a V4 or V5 transaction with an invalid hash type\n- The V5 transaction would be accepted by Zebra nodes but not by `zcashd` nodes (and vice-versa for V4), creating a consensus split in the network.\n\n## Impact\n\n**Consensus Failure**\n\n- **Attack Vector:** Network.\n- **Effect:** Network partition/consensus split.\n- **Scope:** Any Zebra affected Zebra node\n\n## Fixed Versions\n\nThis issue is fixed in Zebra 4.3.1.\n\nThe fix adds the consensus check in the caller of the C++ verification code. It also uses the raw hash type for V4 sighash computations.\n\n## Mitigation\n\nUsers should upgrade to Zebra 4.3.1 or later immediately.\n\nThere are no known workarounds for this issue. Immediate upgrade is the only way to ensure the node remains on the correct consensus path and is protected against malicious chain forks.\n\n## Credits\n\nThanks Alex “Scalar” Sol for finding and reporting the issue, and to @sangsoo-osec who independently found the same issue and demonstrated that the V4 variant was also exploitable.",
9+
"severity": [
10+
{
11+
"type": "CVSS_V4",
12+
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:H/SA:H"
13+
}
14+
],
15+
"affected": [
16+
{
17+
"package": {
18+
"ecosystem": "crates.io",
19+
"name": "zebrad"
20+
},
21+
"ranges": [
22+
{
23+
"type": "ECOSYSTEM",
24+
"events": [
25+
{
26+
"introduced": "0"
27+
},
28+
{
29+
"fixed": "4.3.1"
30+
}
31+
]
32+
}
33+
]
34+
},
35+
{
36+
"package": {
37+
"ecosystem": "crates.io",
38+
"name": "zebra-script"
39+
},
40+
"ranges": [
41+
{
42+
"type": "ECOSYSTEM",
43+
"events": [
44+
{
45+
"introduced": "0"
46+
},
47+
{
48+
"fixed": "5.0.1"
49+
}
50+
]
51+
}
52+
]
53+
}
54+
],
55+
"references": [
56+
{
57+
"type": "WEB",
58+
"url": "https://github.com/ZcashFoundation/zebra/security/advisories/GHSA-8m29-fpq5-89jj"
59+
},
60+
{
61+
"type": "PACKAGE",
62+
"url": "https://github.com/ZcashFoundation/zebra"
63+
}
64+
],
65+
"database_specific": {
66+
"cwe_ids": [
67+
"CWE-573"
68+
],
69+
"severity": "CRITICAL",
70+
"github_reviewed": true,
71+
"github_reviewed_at": "2026-04-18T01:15:24Z",
72+
"nvd_published_at": null
73+
}
74+
}

0 commit comments

Comments
 (0)