Skip to content

Add text on untrusted input to 1.0 #759

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Sakurann merged 5 commits into from
Jul 30, 2026
Merged

Add text on untrusted input to 1.0 #759

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
9873fe5
add text on untrusted input to 1.0
c2bo Jul 13, 2026
9802b7b
Merge branch 'main' into 748-untrusted-input-1-0
c2bo Jul 13, 2026
be0168d
Merge branch 'main' into 748-untrusted-input-1-0
c2bo Jul 14, 2026
99366a0
Clarify input validation requirements for wallets
paulbastian Jul 30, 2026
10c4c0a
Apply suggestion from @lj-raidiam
c2bo Jul 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions 1.0/openid-4-verifiable-presentations-1_0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1934,6 +1934,15 @@ these constraints. The Wallet is not controlled by the Verifier and the Verifier
MUST perform its own security checks on the returned Credentials and
Presentations.

## Parsing of untrusted inputs

Wallets MUST treat all incoming requests as untrusted input. To mitigate injection and resource exhaustion attacks, Wallets MUST implement input validation on the Authorization Request and its enclosed DCQL query.

Wallets SHOULD implement at least the following steps:

* Enforce input validation: Verify that the Authorization Request and DCQL query contain no malformed properties. Unknown parameters MUST be ignored.
* Apply resource limits: Enforce maximum length restrictions on strings, maximum depths for nested objects, and maximum item counts for arrays within the query.

# Privacy Considerations {#privacy-considerations}

Many privacy considerations are specific to the Credential format and associated proof type used in a particular Presentation.
Expand Down Expand Up @@ -3616,6 +3625,7 @@ The technology described in this specification was made available from contribut

-31

* add security considerations on untrusted input
* Clarify that the Wallet does not follow HTTP redirects
* Clarify jwks use parameter
* Clarify nonce entropy requirements
Expand Down
2 changes: 1 addition & 1 deletion 1.1/openid-4-verifiable-presentations-1_1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2001,7 +2001,7 @@ Presentations.

Wallets MUST treat all incoming requests as untrusted input. To mitigate injection and resource exhaustion attacks, Wallets MUST implement input validation on the Authorization Request and its enclosed DCQL query.

Wallets SHOULD implement the following steps:
Wallets SHOULD at least implement the following steps:

* Enforce input validation: Verify that the Authorization Request and DCQL query contain no malformed properties. Unknown parameters MUST be ignored.
* Apply resource limits: Enforce maximum length restrictions on strings, maximum depths for nested objects, and maximum item counts for arrays within the query.
Expand Down
Loading