Approved changes feed: RSS · Atom
cpe:2.3:a:nessshon:tonapi:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Nessshon (6c4fdbf3-0bc8-537d-aa57-86bd49388eef) |
|---|---|
| Product | Tonapi (988a1c0f-8882-53ee-86db-2483d3253d5d) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-54635 |
vulnerable | 2026-09-16 04:33:28.756638 |
pytonapi has a Webhook Custom Path Authentication Bypass
HIGH (7.5)
pytonapi is a Python SDK for TONAPI that provides REST API, streaming, and webhook access to the TON blockchain. From 2.0.0 to 2.2.0, TonapiWebhookDispatcher fails to validate the Authorization header when a webhook handler is registered with the documented path argument, because setup() stores bearer tokens only under the default suffix paths and never adds the custom path to the token map, so self._tokens.get(path) returns None and the authentication guard is skipped. An unauthenticated remote attacker can POST forged payloads to the custom webhook endpoint and trigger victim-defined handlers. This issue is fixed in version 2.2.1.
Published: 2026-07-28T17:09:08.372Z
Updated: 2026-08-11T22:11:09.656Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.