How severe is GHSA-f28g-86hc-823q?

No CVSS score has been assigned to GHSA-f28g-86hc-823q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-f28g-86hc-823q?

GHSA-f28g-86hc-823q affects the following packages: github.com/superfly/tokenizer (Go). Ecosystems affected: Go.

How do I fix GHSA-f28g-86hc-823q?

Update github.com/superfly/tokenizer to 0.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f28g-86hc-823q is resolved across your whole dependency graph.

How do I detect GHSA-f28g-86hc-823q in my Go dependencies?

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

How do I mitigate GHSA-f28g-86hc-823q if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-f28g-86hc-823q?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f28g-86hc-823q can be triaged on real exposure rather than presence alone.

Is GHSA-f28g-86hc-823q actively exploited in the wild?

No public exploit code has been indexed for GHSA-f28g-86hc-823q yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-f28g-86hc-823q published, and has it been updated?

GHSA-f28g-86hc-823q was published on July 13, 2023 and was last updated on May 20, 2024. 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

GHSA-f28g-86hc-823q — tokenizer

Fix: superfly/tokenizer#8

GHSA-f28g-86hc-823q is a security vulnerability in github.com/superfly/tokenizer. A fix is available for github.com/superfly/tokenizer — see the affected versions and patch details below.

Tokenizer vulnerable to client brute-force of token secrets

Also known asGO-2023-1914

Published

Jul 13, 2023

Updated

May 20, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of May 20, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/superfly/tokenizer

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

Impact

Authorized clients, having an inject_processor secret, could brute-force the secret token value by abusing the fmt parameter to the Proxy-Tokenizer header.

Patches

This was fixed in https://github.com/superfly/tokenizer/pull/8 and further mitigated in https://github.com/superfly/tokenizer/pull/9.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/superfly/tokenizer`	all versions	0.0.1`go get github.com/superfly/tokenizer@v0.0.1`

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/superfly/tokenizer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/superfly/tokenizer to 0.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f28g-86hc-823q is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f28g-86hc-823q can be triaged on real exposure rather than presence alone.

Tailored to GHSA-f28g-86hc-823q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Authorized clients, having an `inject_processor` secret, could brute-force the secret token value by abusing the `fmt` parameter to the `Proxy-Tokenizer` header. ### Patches This was fixed in https://github.com/superfly/tokenizer/pull/8 and further mitigated in https://github.com/superfly/tokenizer/pull/9.

O3 Security · Impact-Aware SCA

Is GHSA-f28g-86hc-823q in your dependencies?

O3 Security finds GHSA-f28g-86hc-823q across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works