What is CVE-2022-4396?

CVE-2022-4396 is a medium-severity cross-site scripting (XSS) vulnerability in pyRdfa3 (pip), affecting versions <= 3.5.3. It is fixed in 3.6.2. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is CVE-2022-4396?

CVE-2022-4396 has a CVSS score of 5.4 (Medium). 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 pyRdfa3 are affected by CVE-2022-4396?

pyRdfa3 (pip) versions <= 3.5.3 is affected.

Is there a fix for CVE-2022-4396?

Yes. CVE-2022-4396 is fixed in 3.6.2. Upgrade to this version or later.

Is CVE-2022-4396 exploitable, and should I be worried?

Whether CVE-2022-4396 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-2022-4396 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.

CVE-2022-4396 in pyRdfa3

Q: How severe is CVE-2022-4396?

CVE-2022-4396 has a CVSS score of 5.4 (Medium). 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 pyRdfa3 are affected by CVE-2022-4396?

pyRdfa3 (pip) versions <= 3.5.3 is affected.

Q: Is there a fix for CVE-2022-4396?

Yes. CVE-2022-4396 is fixed in 3.6.2. Upgrade to this version or later.

Q: Is CVE-2022-4396 exploitable, and should I be worried?

Whether CVE-2022-4396 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-2022-4396 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-2022-4396?

Upgrade pyRdfa3 to 3.6.2 or later.

Summary

pyRdfa3 Cross-site Scripting vulnerability

A vulnerability was found in RDFlib pyrdfa3 and classified as problematic. This issue affects the function _get_option of the file pyRdfa/__init__.py. The manipulation leads to cross site scripting. The attack may be initiated remotely. The name of the patch is ffd1d62dd50d5f4190013b39cedcdfbd81f3ce3e. It is recommended to apply a patch to fix this issue. The identifier VDB-215249 was assigned to this vulnerability.

Impact

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2022-4396 has a CVSS score of 5.4 (Medium). The vector is network-reachable, low privileges required, and user interaction required. 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 (3.6.2); upgrading removes the vulnerable code path.

Affected versions

pyRdfa3 (<= 3.5.3)

Security releases

pyRdfa3 → 3.6.2 (pip)

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

Upgrade pyRdfa3 to 3.6.2 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2022-4396? CVE-2022-4396 is a medium-severity cross-site scripting (XSS) vulnerability in pyRdfa3 (pip), affecting versions <= 3.5.3. It is fixed in 3.6.2. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
How severe is CVE-2022-4396? CVE-2022-4396 has a CVSS score of 5.4 (Medium). 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 pyRdfa3 are affected by CVE-2022-4396? pyRdfa3 (pip) versions <= 3.5.3 is affected.
Is there a fix for CVE-2022-4396? Yes. CVE-2022-4396 is fixed in 3.6.2. Upgrade to this version or later.
Is CVE-2022-4396 exploitable, and should I be worried? Whether CVE-2022-4396 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-2022-4396 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-2022-4396? Upgrade pyRdfa3 to 3.6.2 or later.