You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, I'm unsure of any other projects currently using this fork in production and have not independently audited it.
Describe alternatives you've considered
Adopt the new https://github.com/twmb/avro library, which would obviously require a refactor. I have quite high confidence in this library since the maintainer has a couple of high impact projects that they manage.
I see there's already a PR for #1518. I have a working change on my local using the https://github.com/twmb/avro approach, so happy to contribute a change if the aforementioned PR is not accepted.
Two things bearing on the choice between the fork and twmb/avro.
redpanda-data/connect already made this decision: #4195
replaced both linkedin/goavro and hamba/avro with twmb/avro and deleted a
571-line normalisation walker, since type coercion and union handling are native
there.
The fork inherits a soe.Codec.Encode aliasing bug from hamba — filed as iskorotkov/avro#36 with a reproducer. Encode appends onto a shared 10-byte
header slice, so small payloads return aliased buffers and a caller holding two
encodings sees the first mutate. pulsar/schema.go uses Marshal/Unmarshal
rather than soe, so Pulsar is not exposed today, but it is the kind of thing
that arrives with an unmaintained-upstream fork.
Not an argument against #1518 — swapping to the fork fixes the CVE now and is
three call sites. Worth weighing if the choice is being made once.
I fixed multiple CVEs and several other issues, improved performance in some parts & plan to do more fixes and optimizations in the coming months.
If I open a new PR that replaces hamba/avro with my fork will it be merged? Is there a reason the previous one wasn't merged? I understand my fork is relatively new but my company also uses Avro in production extensively and I am interested in maintaining it.
If there are any unresolved issues with my fork or safety concerns - please let me know and I will try to address them.
Activity
[-][CVE] Replace `github.com/hamba/avro` usage.[/-][+][CVE] Replace `github.com/hamba/avro` usage[/+]gregfurman commentedon Aug 5, 2026
I see there's already a PR for #1518. I have a working change on my local using the https://github.com/twmb/avro approach, so happy to contribute a change if the aforementioned PR is not accepted.
slachiewicz commentedon Aug 12, 2026
Two things bearing on the choice between the fork and
twmb/avro.redpanda-data/connectalready made this decision: #4195replaced both
linkedin/goavroandhamba/avrowithtwmb/avroand deleted a571-line normalisation walker, since type coercion and union handling are native
there.
The fork inherits a
soe.Codec.Encodealiasing bug fromhamba— filed asiskorotkov/avro#36 with a reproducer.
Encodeappends onto a shared 10-byteheader slice, so small payloads return aliased buffers and a caller holding two
encodings sees the first mutate.
pulsar/schema.gousesMarshal/Unmarshalrather than
soe, so Pulsar is not exposed today, but it is the kind of thingthat arrives with an unmaintained-upstream fork.
Not an argument against #1518 — swapping to the fork fixes the CVE now and is
three call sites. Worth weighing if the choice is being made once.
iskorotkov commentedon Nov 2, 2026
Hi! I am a maintainer of https://github.com/iskorotkov/avro. I see this issue has stalled & the linked PR #1518 was closed with no resolution.
I fixed multiple CVEs and several other issues, improved performance in some parts & plan to do more fixes and optimizations in the coming months.
If I open a new PR that replaces hamba/avro with my fork will it be merged? Is there a reason the previous one wasn't merged? I understand my fork is relatively new but my company also uses Avro in production extensively and I am interested in maintaining it.
If there are any unresolved issues with my fork or safety concerns - please let me know and I will try to address them.