Is there a reason to consider this leak sensitive and keep this report as a private security bug ?
Seems like it mostly warrants an api hardening patch and it could be fixed as a normal bug.
Is there a reason to consider this leak sensitive and keep this report as a private security bug ?
Seems like it mostly warrants an api hardening patch and it could be fixed as a normal bug.