What is CVE-2023-40023?

CVE-2023-40023 is a high-severity security vulnerability in github.com/yaklang/yaklang (go), affecting versions < 1.2.4-sp2. It is fixed in 1.2.4-sp2.

How severe is CVE-2023-40023?

CVE-2023-40023 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/yaklang/yaklang are affected by CVE-2023-40023?

github.com/yaklang/yaklang (go) versions < 1.2.4-sp2 is affected.

Is there a fix for CVE-2023-40023?

Yes. CVE-2023-40023 is fixed in 1.2.4-sp2. Upgrade to this version or later.

Is CVE-2023-40023 exploitable, and should I be worried?

Whether CVE-2023-40023 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2023-40023 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2023-40023?

Upgrade github.com/yaklang/yaklang to 1.2.4-sp2 or later.

CVE-2023-40023 in github.com/yaklang/yaklang

Q: How severe is CVE-2023-40023?

CVE-2023-40023 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of github.com/yaklang/yaklang are affected by CVE-2023-40023?

github.com/yaklang/yaklang (go) versions < 1.2.4-sp2 is affected.

Q: Is there a fix for CVE-2023-40023?

Yes. CVE-2023-40023 is fixed in 1.2.4-sp2. Upgrade to this version or later.

Q: Is CVE-2023-40023 exploitable, and should I be worried?

Whether CVE-2023-40023 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2023-40023 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2023-40023?

Upgrade github.com/yaklang/yaklang to 1.2.4-sp2 or later.

Summary

Yaklang Plugin's Fuzztag Component Allows Unauthorized Local File Reading

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:

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.

CVE-2023-40023 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.2.4-sp2); upgrading removes the vulnerable code path.

Affected versions

github.com/yaklang/yaklang (< 1.2.4-sp2)

Security releases

github.com/yaklang/yaklang → 1.2.4-sp2 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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

Frequently Asked Questions

What is CVE-2023-40023? CVE-2023-40023 is a high-severity security vulnerability in github.com/yaklang/yaklang (go), affecting versions < 1.2.4-sp2. It is fixed in 1.2.4-sp2.
How severe is CVE-2023-40023? CVE-2023-40023 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of github.com/yaklang/yaklang are affected by CVE-2023-40023? github.com/yaklang/yaklang (go) versions < 1.2.4-sp2 is affected.
Is there a fix for CVE-2023-40023? Yes. CVE-2023-40023 is fixed in 1.2.4-sp2. Upgrade to this version or later.
Is CVE-2023-40023 exploitable, and should I be worried? Whether CVE-2023-40023 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2023-40023 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2023-40023? Upgrade github.com/yaklang/yaklang to 1.2.4-sp2 or later.