- Top reward
- $1,500
- Top severity paid
- Critical
- Assets in scope
- 12
- Public CVEs
- 39
- Last change
- No changes yet
At a glance
What to know before you start testing.
- Pays from $1,500
- for critical bugs.
- Report on Sorona
- Submit through the program page.
- Partial safe harbor
- Some legal protection; read the terms.
- Publish after a fix
- Coordinate the timing with the company.
Rewards
What Sorona lists as the payout for each severity.
| Severity | Relative size | Reward |
|---|---|---|
| Critical | $1,500+ | |
| High | $700+ | |
| Medium | $300+ | |
| Low |
|
$100 $100 / 1 month Claude Max |
- Safe harbor
-
Partial
Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf.
Summarised with AI from the program policy on Sorona, read 12 Nov 2026, and checked word for word against it. Read the original
Scope
12 assets you may test, 5 excluded.
Web 1
- https://github.com/libsndfile/libsndfile
Products and areas 11
- AIFF and AIFC, CAF, AU, W64, RF64 and the other mainstream containers
- Metadata and string handling: broadcast wave extension chunks, cart chunks, cue and instrument chunks, LOOP data and ID3 handling
- The ADPCM family in full, covering IMA, MS, NMS, VOX and the G.72x variants, the area several of the recent findings landed in
- The bundled command-line programs that ship with the library and run the same parsers
- The command interface and everything it can be asked to change about an open file
- The long tail of legacy formats compiled in by default, including IRCAM, AVR, HTK, PAF, SVX, SDS, MAT4 and MAT5, VOC, WVE, XI and NIST Sphere
- The Ogg-backed paths and the FLAC and Vorbis handling libsndfile drives through them
- The other codec handlers: GSM 6.10, ALAC, MPEG audio, A-law and mu-law, and the raw PCM paths with their endianness and bit-depth conversions
- The policy asks for private email reports and names 1.1.x as the supported line. It carves nothing out of the library, so every format handler and every entry point is in
- The public API and the virtual I/O callback interface, which lets a caller feed the library from memory or from a socket rather than from a file
- The RIFF and WAV container layer: chunk walking, chunk size handling and the chunk read and write helpers
Out of scope (5)
- Bugs in libFLAC, libvorbis, libogg or libmpg123 rather than in libsndfile's use of them
- Bugs in the Python wrappers, soundfile and librosa, which are separate projects on top of this library
- Build system and packaging issues rather than upstream library code
- Format-support gaps and files libsndfile declines to open
- The project publishes no exclusion list, so the items above are genuine boundaries rather than policy text
Rules
What the policy asks of you, and the bug types it won't reward, quoted from Sorona's policy.
While testing
-
Submit through sorona.xyz.
-
Send the report privately to the address in SECURITY.md and say how you want to be credited
-
test against master and quote the commit hash you built
-
Attach the file.
-
Say which format handler you landed in
Summarised with AI from the program policy on Sorona, read 12 Nov 2026, and checked word for word against it. Read the original
Changes
Tracked since 11 Nov 2026. Last checked 1 hour ago.
No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.
Public CVEs
Published vulnerabilities in this vendor's products, from the NVD.
Sorona credits this project with 39 CVEs, 3 of them recent. The individual records appear here after the next sync.
Original policy
Copied from sorona.xyz on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.
Skip to content What this pays This project runs no bounty of its own. sorona.xyz pays you directly on qualified, reproduced findings. Severity │ sorona.xyz pays Critical │ $1,500+ High │ $700+ Medium │ $300+ Low │ $100 / 1 month Claude Max Submit a vulnerability CVE history 3 Last 12 months 39 Lifetime Memory safety 55 % Parsing/validation 25 % Denial of service 15 % Info disclosure 5 % Latest advisories Loading the feed Overview libsndfile is the C library that reads and writes WAV, AIFF, FLAC, CAF and dozens of other audio formats. It sits under Audacity and under Python's soundfile and librosa packages, which puts it at the front door of nearly every machine-learning audio pipeline that accepts a file from a user. CVE-2026-37555 in the IMA ADPCM WAV path is a recent example of what arrives there. The last five commits are all memory-safety fixes from outside contributors, yet no release has shipped since 1.2.2 in August 2023 and the private channel is one maintainer's personal address. Nobody pays for any of it, so sorona.xyz pays you directly on qualified, reproduced findings. In scope The policy asks for private email reports and names 1.1.x as the supported line. It carves nothing out of the library, so every format handler and every entry point is in The RIFF and WAV container layer: chunk walking, chunk size handling and the chunk read and write helpers AIFF and AIFC, CAF, AU, W64, RF64 and the other mainstream containers The Ogg-backed paths and the FLAC and Vorbis handling libsndfile drives through them The ADPCM family in full, covering IMA, MS, NMS, VOX and the G.72x variants, the area several of the recent findings landed in The other codec handlers: GSM 6.10, ALAC, MPEG audio, A-law and mu-law, and the raw PCM paths with their endianness and bit-depth conversions The long tail of legacy formats compiled in by default, including IRCAM, AVR, HTK, PAF, SVX, SDS, MAT4 and MAT5, VOC, WVE, XI and NIST Sphere Metadata and string handling: broadcast wave extension chunks, cart chunks, cue and instrument chunks, LOOP data and ID3 handling The public API and the virtual I/O callback interface, which lets a caller feed the library from memory or from a socket rather than from a file The command interface and everything it can be asked to change about an open file The bundled command-line programs that ship with the library and run the same parsers Out of scope Bugs in libFLAC, libvorbis, libogg or libmpg123 rather than in libsndfile's use of them Bugs in the Python wrappers, soundfile and librosa, which are separate projects on top of this library Build system and packaging issues rather than upstream library code Format-support gaps and files libsndfile declines to open The project publishes no exclusion list, so the items above are genuine boundaries rather than policy text Most-valued findings Heap corruption in a container chunk reader or writer. This is the live class: the current commit stream carries a heap overflow in psf_save_write_chunk and an out-of-bounds write in nms_adpcm, both from outside contributors and both unrewarded The ADPCM family, where CVE-2026-37555 landed in the IMA ADPCM WAV path. These decoders do byte-level index maths on values pulled straight out of the file The legacy handlers nobody uses but everyone compiles in, the CVE-2025-52194 shape in the IRCAM path. Reach beats popularity here, since the format is selected from the file's own header rather than by the caller Resource leaks and unbounded allocation reachable from a crafted header, the CVE-2025-56226 shape. In an ingestion pipeline that is a denial of service against the service rather than a nuisance on a desktop Anything reachable through a plain open call on an untrusted file with no format hint, since that is exactly how the Python wrappers call this library across millions of monthly installs Bugs reachable through the virtual I/O callbacks, where the input is a stream a server is receiving rather than a file on disk Program rules Submit through sorona.xyz. This project runs no bounty of its own; we validate, coordinate disclosure with the maintainers, and pay you directly. Send the report privately to the address in SECURITY.md and say how you want to be credited, which is what the policy asks for Expect latency. The channel is a single maintainer's personal email rather than a project alias, and it is the only private route the project offers The policy names 1.1.x as supported while the newest release is 1.2.2 from August 2023, so test against master and quote the commit hash you built Attach the file. Every interesting bug in this library is a file, and a minimal one gets triaged much faster against a backlog of over 200 open issues Say which format handler you landed in, since the container layer and the codec layer fail differently and the fix goes in different places There is no reward. The policy offers credit and nothing else Disclosure Coordinated privately by email with one maintainer. There is no advisory stream, no published timeline and no fixed embargo, and fixes have been landing as ordinary commits without a release behind them since 2023, so a merged fix does not mean a shipped fix. Distributions carry 1.2.2 and backport selectively, so treat the downstream tail as long and hold the detail accordingly. Safe harbor Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf. You are responsible for understanding and following the laws that apply to you, wherever you are, and for staying within any scope the project has defined. Submit a vulnerability