Every CVESearch/Get API key

GHSA-5xgj-pmjj-gw49

RISC Zero zkVM notes on zero-knowledge

No score

GHSA-5xgj-pmjj-gw49 is a vulnerability with no CVSS score yet in risc0-zkvm, published July 15, 2024. No source lists public exploit code. No source names a fixed version.

What does this mean?
Severity
UnratedNo CVSS score yet
Exploit chance
UnscoredNo EPSS score yet
Exploitation
None knownNot on CISA’s or ENISA’s lists
Fixed in
No fix listedNo source names one

Description

RISC Zero zkVM was designed from its inception to provide three main guarantees:

  1. Computational integrity: that a given software program executed correctly.
  2. Succinctness: that the proof of execution does not grow in relation to the program being executed.
  3. Zero Knowledge: that details of the program execution are not visible within the proof of program execution.

Ulrich Habock and Al Kindi have released new research that indicates that several STARK implementations -including our RISC Zero zkVM- do not meet the requirements to assert the specific property of zero knowledge provably.

While a vast majority of real-world applications that leverage RISC Zero zkVM or similar systems depend primarily on computational integrity and succinctness, a subset of applications critically depend on the privacy guarantees provided by zero-knowledge; and for those use cases, users are cautioned to understand the research and make informed decisions based on the risks outlined in using an impacted system.

Although the maintainers are not aware of any attacks that can take advantage of this potential weakness, they are working to proactively address this discovery as quickly as possible.

Affected packages

Affected packages
PackageAffectedFixed
risc0-zkvm
crates.io
through 1.0.2None known

What each source reports

GitHub AdvisoriesNo score

RISC Zero zkVM notes on zero-knowledge

RISC Zero zkVM was designed from its inception to provide three main guarantees:

  1. Computational integrity: that a given software program executed correctly.
  2. Succinctness: that the proof of execution does not grow in relation to the program being executed.
  3. Zero Knowledge: that details of the program execution are not visible within the proof of program execution.

Ulrich Habock and Al Kindi have released new research that indicates that several STARK implementations -including our RISC Zero zkVM- do not meet the requirements to assert the specific property of zero knowledge provably.

While a vast majority of real-world applications that leverage RISC Zero zkVM or similar systems depend primarily on computational integrity and succinctness, a subset of applications critically depend on the privacy guarantees provided by zero-knowledge; and for those use cases, users are cautioned to understand the research and make informed decisions based on the risks outlined in using an impacted system.

Although the maintainers are not aware of any attacks that can take advantage of this potential weakness, they are working to proactively address this discovery as quickly as possible.

Record
GHSA-5xgj-pmjj-gw49
Updated
2026-11-02
OSVNo score

RISC Zero zkVM notes on zero-knowledge

RISC Zero zkVM was designed from its inception to provide three main guarantees:

  1. Computational integrity: that a given software program executed correctly.
  2. Succinctness: that the proof of execution does not grow in relation to the program being executed.
  3. Zero Knowledge: that details of the program execution are not visible within the proof of program execution.

Ulrich Habock and Al Kindi have released new research that indicates that several STARK implementations -including our RISC Zero zkVM- do not meet the requirements to assert the specific property of zero knowledge provably.

While a vast majority of real-world applications that leverage RISC Zero zkVM or similar systems depend primarily on computational integrity and succinctness, a subset of applications critically depend on the privacy guarantees provided by zero-knowledge; and for those use cases, users are cautioned to understand the research and make informed decisions based on the risks outlined in using an impacted system.

Although the maintainers are not aware of any attacks that can take advantage of this potential weakness, they are working to proactively address this discovery as quickly as possible.

Record
GHSA-5xgj-pmjj-gw49
Updated
2026-11-02

History

History
RecordedChangedSources
first indexedGitHub Advisories, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

References

MoveEnter Open