NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

Yaklang Plugin's Fuzztag Component Allows Unauthorized Local File ReadingGHSA-xvhg-w6qc-m3qq

HIGHFix: yaklang/yaklang#295

GHSA-xvhg-w6qc-m3qq is a high-severity (CVSS 7.5) Information Exposure vulnerability in github.com/yaklang/yaklang. A fix is available for github.com/yaklang/yaklang — see the affected versions and patch details below.

Also known asCVE-2023-40023GO-2023-2011
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-xvhg-w6qc-m3qq.

EPSS Exploitation Probability

via FIRST.org ↗
1.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs64th percentile — riskier than 64% of all scored CVEsHighest risk
0.00%0.52%1.03%1.55%0.2%1.0%May 26Sep 26Nov 26

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/yaklang/yaklang

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

The Yak Engine has been found to contain a local file inclusion (LFI) vulnerability. This vulnerability allows attackers to include files from the server's local file system through the web application. When exploited, this can lead to the unintended exposure of sensitive data, potential remote code execution, or other security breaches. Users utilizing versions of the Yak Engine prior to 1.2.4-sp1 are impacted.

Patches

The vulnerability has been addressed and patched. Users are advised to upgrade to Yak Engine version 1.2.4-sp1 immediately. The patch can be viewed and reviewed at this PR: https://github.com/yaklang/yaklang/pull/295，https://github.com/yaklang/yaklang/pull/296

Workarounds

Currently, the most effective solution is to upgrade to the patched version of Yak Engine (1.2.4-sp1). Users are also advised to avoid exposing vulnerable versions to untrusted input and to closely monitor any unexpected server behavior until they can upgrade.

References

For more details on the vulnerability and the corresponding patch, please visit the following link:

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/yaklang/yaklangall versions1.2.4-sp2go get github.com/yaklang/yaklang@v1.2.4-sp2

Affected Products

1 product · 26 configurations
Application
yaklangyaklang
5 versions
1.2.01.2.11.2.21.2.31.2.4

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

    Update github.com/yaklang/yaklang to 1.2.4-sp2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xvhg-w6qc-m3qq is resolved across your whole dependency graph.

  3. Workarounds

    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

### Impact The Yak Engine has been found to contain a local file inclusion (LFI) vulnerability. This vulnerability allows attackers to include files from the server's local file system through the web application. When exploited, this can lead to the unintended exposure of sensitive data, potential remote code execution, or other security breaches. Users utilizing versions of the Yak Engine prior to 1.2.4-sp1 are impacted. ### Patches The vulnerability has been addressed and patched. Users are advised to upgrade to Yak Engine version 1.2.4-sp1 immediately. The patch can be viewed and review
O3 Security · Impact-Aware SCA

Is GHSA-xvhg-w6qc-m3qq in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Yaklang Plugin's Fuzztag Component Allows…