{"id":"CVE-2020-26243","aliases":["DEBIAN-CVE-2020-26243","GHSA-85rr-4rh9-hhwh","PYSEC-2026-684","UBUNTU-CVE-2020-26243"],"summary":"Memory leak in nanopb","published_at":"2020-11-25T00:00:00Z","modified_at":"2026-10-26T12:01:06.842268Z","products":[{"slug":"rhel","name":"Red Hat Enterprise Linux","category":"red-hat"}],"rating":{"severity":"high","score":7.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","attack_path":"internet_unauthenticated","user_interaction":false,"malicious":false,"red_hat":"Important","vendor_ratings":[{"source":"SUSE","rating":"important"},{"source":"Ubuntu","rating":"medium"},{"source":"Red Hat","rating":"Important"}]},"fix_available":false,"kev":{"listed":false,"ransomware":false},"public_exploit":false,"exploits":[],"epss":{"score":0.026639999821782112,"percentile":0.8603799939155579,"date":"2026-11-19T00:00:00Z"},"priority":9.5,"details":"Nanopb is a small code-size Protocol Buffers implementation. In Nanopb before versions 0.4.4 and 0.3.9.7, decoding specifically formed message can leak memory if dynamic allocation is enabled and an oneof field contains a static submessage that contains a dynamic field, and the message being decoded contains the submessage multiple times. This is rare in normal messages, but it is a concern when untrusted data is parsed. This is fixed in versions 0.3.9.7 and 0.4.4. The following workarounds are available: 1) Set the option `no_unions` for the oneof field. This will generate fields as separate instead of C union, and avoids triggering the problematic code. 2) Set the type of the submessage field inside oneof to `FT_POINTER`. This way the whole submessage will be dynamically allocated and the problematic code is not executed. 3) Use an arena allocator for nanopb, to make sure all memory can be released afterwards.","affected_stack":[{"ecosystem":"Red Hat:service_mesh:1","package":"servicemesh-proxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"provider":"redhat-vex","source":"CVE-2020-26243","relation":"self"}],"affected_other":[{"ecosystem":"CVE","package":"nanopb/nanopb","versions":["< 0.3.9.7",">= 0.4.0, < 0.4.4"],"provider":"cvelistv5","source":"CVE-2020-26243","relation":"self"},{"ecosystem":"Debian:12","package":"nanopb","purl":"pkg:deb/debian/nanopb?arch=source&distro=bookworm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.4-1"}]}],"fixed":["0.4.4-1"],"provider":"osv","source":"DEBIAN-CVE-2020-26243","relation":"self"},{"ecosystem":"Debian:13","package":"nanopb","purl":"pkg:deb/debian/nanopb?arch=source&distro=trixie","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.4-1"}]}],"fixed":["0.4.4-1"],"provider":"osv","source":"DEBIAN-CVE-2020-26243","relation":"self"},{"ecosystem":"Debian:14","package":"nanopb","purl":"pkg:deb/debian/nanopb?arch=source&distro=forky","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.4-1"}]}],"fixed":["0.4.4-1"],"provider":"osv","source":"DEBIAN-CVE-2020-26243","relation":"self"},{"ecosystem":"NVD","package":"nanopb_project:nanopb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.3.9.7"}]},{"type":"ECOSYSTEM","events":[{"introduced":"0.4.0"},{"fixed":"0.4.4"}]}],"fixed":["0.3.9.7","0.4.4"],"provider":"nvd","source":"CVE-2020-26243","relation":"self"},{"ecosystem":"PyPI","package":"nanopb","purl":"pkg:pypi/nanopb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.4.0"},{"fixed":"0.4.4"}]}],"versions":["0.4.0","0.4.1","0.4.1.dev1003","0.4.1.dev1007","0.4.1.dev1012","0.4.1.dev1013","0.4.1.dev1017","0.4.1.dev1036","0.4.1.dev959","0.4.1.dev961","0.4.1.dev962","0.4.1.dev964","0.4.1.dev971","0.4.1.dev978","0.4.1.dev980","0.4.1.dev985","0.4.1.dev987","0.4.1.dev988","0.4.1.dev996","0.4.1.dev997","0.4.2","0.4.2.dev1041","0.4.2.dev1043","0.4.2.dev1044","0.4.2.dev1045","0.4.2.dev1048","0.4.2.dev1050","0.4.2.dev1053","0.4.2.dev1054","0.4.2.dev1055","0.4.2.dev1058","0.4.2.dev1059","0.4.2.dev1063","0.4.2.dev1066","0.4.2.dev1070","0.4.2.dev1071","0.4.2.dev1072","0.4.2.dev1076","0.4.2.dev1088","0.4.2.dev1091","0.4.3","0.4.3.dev1128","0.4.3.dev1131","0.4.3.dev1132","0.4.3.dev1133","0.4.3.dev1137","0.4.3.dev1150","0.4.3.dev1164","0.4.3.dev1172","0.4.3.dev1175","0.4.3.dev1177","0.4.4.dev1181","0.4.4.dev1182","0.4.4.dev1184","0.4.4.dev1185","0.4.4.dev1188","0.4.4.dev1192","0.4.4.dev1193"],"fixed":["0.4.4"],"provider":"osv","source":"GHSA-85rr-4rh9-hhwh","relation":"self"},{"ecosystem":"PyPI","package":"nanopb","purl":"pkg:pypi/nanopb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.3.2"},{"fixed":"0.3.9.7"}]}],"versions":["0.3.9.4.post3","0.3.9.5","0.3.9.6"],"fixed":["0.3.9.7"],"provider":"osv","source":"GHSA-85rr-4rh9-hhwh","relation":"self"},{"ecosystem":"PyPI","package":"nanopb","purl":"pkg:pypi/nanopb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.3.2"},{"fixed":"0.3.9.7"},{"introduced":"0.4.0"},{"fixed":"0.4.4"}]}],"versions":["0.3.9.4.post3","0.3.9.5","0.3.9.6","0.4.0","0.4.1","0.4.1.dev1003","0.4.1.dev1007","0.4.1.dev1012","0.4.1.dev1013","0.4.1.dev1017","0.4.1.dev1036","0.4.1.dev959","0.4.1.dev961","0.4.1.dev962","0.4.1.dev964","0.4.1.dev971","0.4.1.dev978","0.4.1.dev980","0.4.1.dev985","0.4.1.dev987","0.4.1.dev988","0.4.1.dev996","0.4.1.dev997","0.4.2","0.4.2.dev1041","0.4.2.dev1043","0.4.2.dev1044","0.4.2.dev1045","0.4.2.dev1048","0.4.2.dev1050","0.4.2.dev1053","0.4.2.dev1054","0.4.2.dev1055","0.4.2.dev1058","0.4.2.dev1059","0.4.2.dev1063","0.4.2.dev1066","0.4.2.dev1070","0.4.2.dev1071","0.4.2.dev1072","0.4.2.dev1076","0.4.2.dev1088","0.4.2.dev1091","0.4.3","0.4.3.dev1128","0.4.3.dev1131","0.4.3.dev1132","0.4.3.dev1133","0.4.3.dev1137","0.4.3.dev1150","0.4.3.dev1164","0.4.3.dev1172","0.4.3.dev1175","0.4.3.dev1177","0.4.4.dev1181","0.4.4.dev1182","0.4.4.dev1184","0.4.4.dev1185","0.4.4.dev1188","0.4.4.dev1192","0.4.4.dev1193"],"fixed":["0.3.9.7","0.4.4"],"provider":"osv","source":"PYSEC-2026-684","relation":"self"},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"nanopb","purl":"pkg:deb/ubuntu/nanopb@0.4.1-1ubuntu0.1~esm1?arch=source&distro=esm-apps/focal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.1-1ubuntu0.1~esm1"}]}],"versions":["0.4.1-1"],"fixed":["0.4.1-1ubuntu0.1~esm1"],"provider":"osv","source":"UBUNTU-CVE-2020-26243","relation":"self"},{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"nanopb","purl":"pkg:deb/ubuntu/nanopb@0.4.1-1ubuntu0.1~esm1?arch=source&distro=esm-apps/focal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.1-1ubuntu0.1~esm1"}]}],"versions":["0.4.1-1"],"fixed":["0.4.1-1ubuntu0.1~esm1"],"provider":"osv","source":"USN-6121-1","relation":"upstream"},{"ecosystem":"openSUSE:Tumbleweed","package":"nanopb","purl":"pkg:rpm/opensuse/nanopb&distro=openSUSE%20Tumbleweed","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.5-1.3"}]}],"fixed":["0.4.5-1.3"],"provider":"osv","source":"openSUSE-SU-2024:11074-1","relation":"upstream"}],"product_status":[{"vendor":"SUSE","product":"openSUSE Tumbleweed","cpe":"cpe:/o:opensuse:tumbleweed","status":"fixed","packages":["libprotobuf-nanopb0","nanopb-devel","nanopb-source"],"package_count":3,"fixed":["libprotobuf-nanopb0-0.4.5-1.3","nanopb-devel-0.4.5-1.3","nanopb-source-0.4.5-1.3"],"advisories":[],"provider":"csaf-suse","source":"CVE-2020-26243"},{"vendor":"Red Hat","product":"OpenShift Service Mesh 1","cpe":"cpe:/a:redhat:service_mesh:1","status":"affected","packages":["servicemesh-proxy"],"package_count":1,"fixed":[],"advisories":[],"note":"Will not fix","provider":"redhat-vex","source":"CVE-2020-26243"}],"records":[{"provider":"csaf-suse","source_id":"openSUSE-SU-2024:11074-1","relation":"upstream","url":"https://www.suse.com/security/cve/CVE-2020-26243/","license":"TLP:CLEAR, mirroring permitted","published_at":"2024-06-15T00:00:00Z","modified_at":"2024-06-15T00:00:00Z","summary":"libprotobuf-nanopb0-0.4.5-1.3 on GA media","details":"libprotobuf-nanopb0-0.4.5-1.3 on GA media\n\nThese are all security issues fixed in the libprotobuf-nanopb0-0.4.5-1.3 package on the GA media of openSUSE Tumbleweed.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L","source":"openSUSE-SU-2024:11074-1"},{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L","source":"openSUSE-SU-2024:11074-1"},{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","source":"openSUSE-SU-2024:11074-1"},{"type":"SUSE","score":"moderate","source":"openSUSE-SU-2024:11074-1"}],"affected":[],"product_status":[],"references":[{"type":"WEB","url":"https://www.suse.com/support/security/rating/"},{"type":"WEB","url":"https://ftp.suse.com/pub/projects/security/csaf/2024/opensuse-su-2024_11074-1.json"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2020-26243/"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2020-5235/"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2021-21401/"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2020-26243"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2020-5235"},{"type":"WEB","url":"https://bugzilla.suse.com/1162647"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2021-21401"}]},{"provider":"osv","source_id":"USN-6121-1","relation":"upstream","url":"https://osv.dev/vulnerability/USN-6121-1","license":"CC-BY-SA-4.0","published_at":"2023-05-30T16:09:29Z","modified_at":"2026-04-22T10:35:16.428853Z","summary":"nanopb vulnerabilities","details":"It was discovered that Nanopb incorrectly handled certain decode messages.\nAn attacker could possibly use this cause a denial of service or expose\nsensitive information. (CVE-2020-26243)\n\nIt was discovered that Nanopb incorrectly handled certain decode messages.\nAn attacker could possibly use this issue to cause a denial of service\nor execute arbitrary code. (CVE-2021-21401)","severity":[],"affected":[{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"nanopb","purl":"pkg:deb/ubuntu/nanopb@0.4.1-1ubuntu0.1~esm1?arch=source&distro=esm-apps/focal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.1-1ubuntu0.1~esm1"}]}],"versions":["0.4.1-1"],"fixed":["0.4.1-1ubuntu0.1~esm1"],"provider":"osv","source":"USN-6121-1","relation":"upstream"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://ubuntu.com/security/notices/USN-6121-1"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2020-26243"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2021-21401"}]},{"provider":"osv","source_id":"openSUSE-SU-2024:11074-1","relation":"upstream","url":"https://osv.dev/vulnerability/openSUSE-SU-2024:11074-1","published_at":"2024-06-15T00:00:00Z","modified_at":"2026-02-04T02:52:40.75074Z","summary":"libprotobuf-nanopb0-0.4.5-1.3 on GA media","details":"These are all security issues fixed in the libprotobuf-nanopb0-0.4.5-1.3 package on the GA media of openSUSE Tumbleweed.","severity":[],"affected":[{"ecosystem":"openSUSE:Tumbleweed","package":"nanopb","purl":"pkg:rpm/opensuse/nanopb&distro=openSUSE%20Tumbleweed","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.5-1.3"}]}],"fixed":["0.4.5-1.3"],"provider":"osv","source":"openSUSE-SU-2024:11074-1","relation":"upstream"}],"product_status":[],"references":[{"type":"ADVISORY","url":""},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2020-26243"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2020-5235"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2021-21401"}]},{"provider":"cvelistv5","source_id":"CVE-2020-26243","relation":"self","url":"https://www.cve.org/CVERecord?id=CVE-2020-26243","license":"CC-BY-4.0","published_at":"2020-11-25T16:50:15Z","modified_at":"2024-08-04T15:56:04.801Z","summary":"Memory leak in nanopb","details":"Nanopb is a small code-size Protocol Buffers implementation. In Nanopb before versions 0.4.4 and 0.3.9.7, decoding specifically formed message can leak memory if dynamic allocation is enabled and an oneof field contains a static submessage that contains a dynamic field, and the message being decoded contains the submessage multiple times. This is rare in normal messages, but it is a concern when untrusted data is parsed. This is fixed in versions 0.3.9.7 and 0.4.4. The following workarounds are available: 1) Set the option `no_unions` for the oneof field. This will generate fields as separate instead of C union, and avoids triggering the problematic code. 2) Set the type of the submessage field inside oneof to `FT_POINTER`. This way the whole submessage will be dynamically allocated and the problematic code is not executed. 3) Use an arena allocator for nanopb, to make sure all memory can be released afterwards.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","source":"CVE-2020-26243"}],"affected":[{"ecosystem":"CVE","package":"nanopb/nanopb","versions":["< 0.3.9.7",">= 0.4.0, < 0.4.4"],"provider":"cvelistv5","source":"CVE-2020-26243","relation":"self"}],"product_status":[],"references":[{"type":"WEB","url":"https://github.com/nanopb/nanopb/security/advisories/GHSA-85rr-4rh9-hhwh"},{"type":"WEB","url":"https://github.com/nanopb/nanopb/issues/615"},{"type":"WEB","url":"https://github.com/nanopb/nanopb/commit/4fe23595732b6f1254cfc11a9b8d6da900b55b0c"},{"type":"WEB","url":"https://github.com/nanopb/nanopb/blob/2b48a361786dfb1f63d229840217a93aae064667/CHANGELOG.txt"}]},{"provider":"csaf-suse","source_id":"CVE-2020-26243","relation":"self","url":"https://www.suse.com/security/cve/CVE-2020-26243/","license":"TLP:CLEAR, mirroring permitted","published_at":"2023-02-15T03:53:15Z","modified_at":"2025-03-15T09:38:38Z","summary":"SUSE CVE CVE-2020-26243","details":"SUSE CVE-2020-26243\n\nNanopb is a small code-size Protocol Buffers implementation. In Nanopb before versions 0.4.4 and 0.3.9.7, decoding specifically formed message can leak memory if dynamic allocation is enabled and an oneof field contains a static submessage that contains a dynamic field, and the message being decoded contains the submessage multiple times. This is rare in normal messages, but it is a concern when untrusted data is parsed. This is fixed in versions 0.3.9.7 and 0.4.4. The following workarounds are available: 1) Set the option `no_unions` for the oneof field. This will generate fields as separate instead of C union, and avoids triggering the problematic code. 2) Set the type of the submessage field inside oneof to `FT_POINTER`. This way the whole submessage will be dynamically allocated and the problematic code is not executed. 3) Use an arena allocator for nanopb, to make sure all memory can be released afterwards.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","source":"CVE-2020-26243"},{"type":"SUSE","score":"important","source":"CVE-2020-26243"}],"affected":[],"product_status":[{"vendor":"SUSE","product":"openSUSE Tumbleweed","cpe":"cpe:/o:opensuse:tumbleweed","status":"fixed","packages":["libprotobuf-nanopb0","nanopb-devel","nanopb-source"],"package_count":3,"fixed":["libprotobuf-nanopb0-0.4.5-1.3","nanopb-devel-0.4.5-1.3","nanopb-source-0.4.5-1.3"],"advisories":[],"provider":"csaf-suse","source":"CVE-2020-26243"}],"references":[{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2020-26243"},{"type":"WEB","url":"https://www.suse.com/support/security/rating/"}]},{"provider":"nvd","source_id":"CVE-2020-26243","relation":"self","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-26243","severity":[],"affected":[{"ecosystem":"NVD","package":"nanopb_project:nanopb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.3.9.7"}]},{"type":"ECOSYSTEM","events":[{"introduced":"0.4.0"},{"fixed":"0.4.4"}]}],"fixed":["0.3.9.7","0.4.4"],"provider":"nvd","source":"CVE-2020-26243","relation":"self"}],"product_status":[],"references":[]},{"provider":"osv","source_id":"DEBIAN-CVE-2020-26243","relation":"self","url":"https://osv.dev/vulnerability/DEBIAN-CVE-2020-26243","published_at":"2020-11-25T17:15:12.2Z","modified_at":"2026-10-26T12:01:06.842268Z","details":"Nanopb is a small code-size Protocol Buffers implementation. In Nanopb before versions 0.4.4 and 0.3.9.7, decoding specifically formed message can leak memory if dynamic allocation is enabled and an oneof field contains a static submessage that contains a dynamic field, and the message being decoded contains the submessage multiple times. This is rare in normal messages, but it is a concern when untrusted data is parsed. This is fixed in versions 0.3.9.7 and 0.4.4. The following workarounds are available: 1) Set the option `no_unions` for the oneof field. This will generate fields as separate instead of C union, and avoids triggering the problematic code. 2) Set the type of the submessage field inside oneof to `FT_POINTER`. This way the whole submessage will be dynamically allocated and the problematic code is not executed. 3) Use an arena allocator for nanopb, to make sure all memory can be released afterwards.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","source":"DEBIAN-CVE-2020-26243"}],"affected":[{"ecosystem":"Debian:12","package":"nanopb","purl":"pkg:deb/debian/nanopb?arch=source&distro=bookworm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.4-1"}]}],"fixed":["0.4.4-1"],"provider":"osv","source":"DEBIAN-CVE-2020-26243","relation":"self"},{"ecosystem":"Debian:13","package":"nanopb","purl":"pkg:deb/debian/nanopb?arch=source&distro=trixie","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.4-1"}]}],"fixed":["0.4.4-1"],"provider":"osv","source":"DEBIAN-CVE-2020-26243","relation":"self"},{"ecosystem":"Debian:14","package":"nanopb","purl":"pkg:deb/debian/nanopb?arch=source&distro=forky","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.4-1"}]}],"fixed":["0.4.4-1"],"provider":"osv","source":"DEBIAN-CVE-2020-26243","relation":"self"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://security-tracker.debian.org/tracker/CVE-2020-26243"}]},{"provider":"osv","source_id":"GHSA-85rr-4rh9-hhwh","relation":"self","url":"https://osv.dev/vulnerability/GHSA-85rr-4rh9-hhwh","license":"CC-BY-4.0","published_at":"2020-11-25T16:53:27Z","modified_at":"2026-07-08T06:00:09.403204Z","summary":"Memory leak in Nanopb","details":"### Impact\nDecoding specifically formed message can leak memory if dynamic allocation is enabled and an oneof field contains a static submessage that contains a dynamic field, and the message being decoded contains the submessage multiple times. This is rare in normal messages, but it is a concern when untrusted data is parsed.\n\n### Patches\nPreliminary patch is [available on git](https://github.com/nanopb/nanopb/commit/edf6dcbffee4d614ac0c2c1b258ab95185bdb6e9) and problem will be patched in versions 0.3.9.7 and 0.4.4 once testing has been completed.\n\n### Workarounds\nFollowing workarounds are available:\n* Set the option `no_unions` for the oneof field. This will generate fields as separate instead of C union, and avoids triggering the problematic code.\n* Set the type of the submessage field inside oneof to `FT_POINTER`. This way the whole submessage will be dynamically allocated and the problematic code is not executed.\n* Use an arena allocator for nanopb, to make sure all memory can be released afterwards.\n\n### References\nBug report: https://github.com/nanopb/nanopb/issues/615\n\n### For more information\nIf you have any questions or comments about this advisory, comment on the bug report linked above.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","source":"GHSA-85rr-4rh9-hhwh"}],"affected":[{"ecosystem":"PyPI","package":"nanopb","purl":"pkg:pypi/nanopb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.4.0"},{"fixed":"0.4.4"}]}],"versions":["0.4.0","0.4.1","0.4.1.dev1003","0.4.1.dev1007","0.4.1.dev1012","0.4.1.dev1013","0.4.1.dev1017","0.4.1.dev1036","0.4.1.dev959","0.4.1.dev961","0.4.1.dev962","0.4.1.dev964","0.4.1.dev971","0.4.1.dev978","0.4.1.dev980","0.4.1.dev985","0.4.1.dev987","0.4.1.dev988","0.4.1.dev996","0.4.1.dev997","0.4.2","0.4.2.dev1041","0.4.2.dev1043","0.4.2.dev1044","0.4.2.dev1045","0.4.2.dev1048","0.4.2.dev1050","0.4.2.dev1053","0.4.2.dev1054","0.4.2.dev1055","0.4.2.dev1058","0.4.2.dev1059","0.4.2.dev1063","0.4.2.dev1066","0.4.2.dev1070","0.4.2.dev1071","0.4.2.dev1072","0.4.2.dev1076","0.4.2.dev1088","0.4.2.dev1091","0.4.3","0.4.3.dev1128","0.4.3.dev1131","0.4.3.dev1132","0.4.3.dev1133","0.4.3.dev1137","0.4.3.dev1150","0.4.3.dev1164","0.4.3.dev1172","0.4.3.dev1175","0.4.3.dev1177","0.4.4.dev1181","0.4.4.dev1182","0.4.4.dev1184","0.4.4.dev1185","0.4.4.dev1188","0.4.4.dev1192","0.4.4.dev1193"],"fixed":["0.4.4"],"provider":"osv","source":"GHSA-85rr-4rh9-hhwh","relation":"self"},{"ecosystem":"PyPI","package":"nanopb","purl":"pkg:pypi/nanopb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.3.2"},{"fixed":"0.3.9.7"}]}],"versions":["0.3.9.4.post3","0.3.9.5","0.3.9.6"],"fixed":["0.3.9.7"],"provider":"osv","source":"GHSA-85rr-4rh9-hhwh","relation":"self"}],"product_status":[],"references":[{"type":"WEB","url":"https://github.com/nanopb/nanopb/security/advisories/GHSA-85rr-4rh9-hhwh"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-26243"},{"type":"WEB","url":"https://github.com/nanopb/nanopb/issues/615"},{"type":"WEB","url":"https://github.com/nanopb/nanopb/commit/4fe23595732b6f1254cfc11a9b8d6da900b55b0c"},{"type":"WEB","url":"https://github.com/nanopb/nanopb/blob/2b48a361786dfb1f63d229840217a93aae064667/CHANGELOG.txt"}]},{"provider":"osv","source_id":"PYSEC-2026-684","relation":"self","url":"https://osv.dev/vulnerability/PYSEC-2026-684","license":"CC-BY-4.0","published_at":"2026-07-02T14:13:09.752037Z","modified_at":"2026-07-06T08:00:39.967579Z","summary":"Memory leak in Nanopb","details":"### Impact\nDecoding specifically formed message can leak memory if dynamic allocation is enabled and an oneof field contains a static submessage that contains a dynamic field, and the message being decoded contains the submessage multiple times. This is rare in normal messages, but it is a concern when untrusted data is parsed.\n\n### Patches\nPreliminary patch is [available on git](https://github.com/nanopb/nanopb/commit/edf6dcbffee4d614ac0c2c1b258ab95185bdb6e9) and problem will be patched in versions 0.3.9.7 and 0.4.4 once testing has been completed.\n\n### Workarounds\nFollowing workarounds are available:\n* Set the option `no_unions` for the oneof field. This will generate fields as separate instead of C union, and avoids triggering the problematic code.\n* Set the type of the submessage field inside oneof to `FT_POINTER`. This way the whole submessage will be dynamically allocated and the problematic code is not executed.\n* Use an arena allocator for nanopb, to make sure all memory can be released afterwards.\n\n### References\nBug report: https://github.com/nanopb/nanopb/issues/615\n\n### For more information\nIf you have any questions or comments about this advisory, comment on the bug report linked above.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","source":"PYSEC-2026-684"}],"affected":[{"ecosystem":"PyPI","package":"nanopb","purl":"pkg:pypi/nanopb","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0.3.2"},{"fixed":"0.3.9.7"},{"introduced":"0.4.0"},{"fixed":"0.4.4"}]}],"versions":["0.3.9.4.post3","0.3.9.5","0.3.9.6","0.4.0","0.4.1","0.4.1.dev1003","0.4.1.dev1007","0.4.1.dev1012","0.4.1.dev1013","0.4.1.dev1017","0.4.1.dev1036","0.4.1.dev959","0.4.1.dev961","0.4.1.dev962","0.4.1.dev964","0.4.1.dev971","0.4.1.dev978","0.4.1.dev980","0.4.1.dev985","0.4.1.dev987","0.4.1.dev988","0.4.1.dev996","0.4.1.dev997","0.4.2","0.4.2.dev1041","0.4.2.dev1043","0.4.2.dev1044","0.4.2.dev1045","0.4.2.dev1048","0.4.2.dev1050","0.4.2.dev1053","0.4.2.dev1054","0.4.2.dev1055","0.4.2.dev1058","0.4.2.dev1059","0.4.2.dev1063","0.4.2.dev1066","0.4.2.dev1070","0.4.2.dev1071","0.4.2.dev1072","0.4.2.dev1076","0.4.2.dev1088","0.4.2.dev1091","0.4.3","0.4.3.dev1128","0.4.3.dev1131","0.4.3.dev1132","0.4.3.dev1133","0.4.3.dev1137","0.4.3.dev1150","0.4.3.dev1164","0.4.3.dev1172","0.4.3.dev1175","0.4.3.dev1177","0.4.4.dev1181","0.4.4.dev1182","0.4.4.dev1184","0.4.4.dev1185","0.4.4.dev1188","0.4.4.dev1192","0.4.4.dev1193"],"fixed":["0.3.9.7","0.4.4"],"provider":"osv","source":"PYSEC-2026-684","relation":"self"}],"product_status":[],"references":[{"type":"WEB","url":"https://github.com/nanopb/nanopb/security/advisories/GHSA-85rr-4rh9-hhwh"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-26243"},{"type":"WEB","url":"https://github.com/nanopb/nanopb/issues/615"},{"type":"WEB","url":"https://github.com/nanopb/nanopb/commit/4fe23595732b6f1254cfc11a9b8d6da900b55b0c"},{"type":"WEB","url":"https://github.com/nanopb/nanopb/blob/2b48a361786dfb1f63d229840217a93aae064667/CHANGELOG.txt"},{"type":"PACKAGE","url":"https://pypi.org/project/nanopb"},{"type":"ADVISORY","url":"https://github.com/advisories/GHSA-85rr-4rh9-hhwh"}]},{"provider":"osv","source_id":"UBUNTU-CVE-2020-26243","relation":"self","url":"https://osv.dev/vulnerability/UBUNTU-CVE-2020-26243","license":"CC-BY-SA-4.0","published_at":"2020-11-25T17:15:00Z","modified_at":"2026-04-22T12:36:20.739465Z","details":"Nanopb is a small code-size Protocol Buffers implementation. In Nanopb before versions 0.4.4 and 0.3.9.7, decoding specifically formed message can leak memory if dynamic allocation is enabled and an oneof field contains a static submessage that contains a dynamic field, and the message being decoded contains the submessage multiple times. This is rare in normal messages, but it is a concern when untrusted data is parsed. This is fixed in versions 0.3.9.7 and 0.4.4. The following workarounds are available: 1) Set the option `no_unions` for the oneof field. This will generate fields as separate instead of C union, and avoids triggering the problematic code. 2) Set the type of the submessage field inside oneof to `FT_POINTER`. This way the whole submessage will be dynamically allocated and the problematic code is not executed. 3) Use an arena allocator for nanopb, to make sure all memory can be released afterwards.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","source":"UBUNTU-CVE-2020-26243"},{"type":"Ubuntu","score":"medium","source":"UBUNTU-CVE-2020-26243"}],"affected":[{"ecosystem":"Ubuntu:Pro:20.04:LTS","package":"nanopb","purl":"pkg:deb/ubuntu/nanopb@0.4.1-1ubuntu0.1~esm1?arch=source&distro=esm-apps/focal","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.4.1-1ubuntu0.1~esm1"}]}],"versions":["0.4.1-1"],"fixed":["0.4.1-1ubuntu0.1~esm1"],"provider":"osv","source":"UBUNTU-CVE-2020-26243","relation":"self"}],"product_status":[],"references":[{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2020-26243"},{"type":"REPORT","url":"https://github.com/nanopb/nanopb/security/advisories/GHSA-85rr-4rh9-hhwh"},{"type":"REPORT","url":"https://github.com/nanopb/nanopb/commit/edf6dcbffee4d614ac0c2c1b258ab95185bdb6e9"},{"type":"REPORT","url":"https://github.com/nanopb/nanopb/issues/615"},{"type":"REPORT","url":"https://github.com/nanopb/nanopb/blob/2b48a361786dfb1f63d229840217a93aae064667/CHANGELOG.txt"},{"type":"REPORT","url":"https://github.com/nanopb/nanopb/commit/4fe23595732b6f1254cfc11a9b8d6da900b55b0c"},{"type":"ADVISORY","url":"https://ubuntu.com/security/notices/USN-6121-1"},{"type":"REPORT","url":"https://www.cve.org/CVERecord?id=CVE-2020-26243"}]},{"provider":"redhat-vex","source_id":"CVE-2020-26243","relation":"self","url":"https://access.redhat.com/security/cve/CVE-2020-26243","license":"CC-BY-4.0","published_at":"2020-11-25T00:00:00Z","modified_at":"2026-02-02T07:28:11.514562Z","summary":"nanopb: oneof fields with PB_ENABLE_MALLOC can leak memory","details":"A flaw was found nanopd. If dynamic allocation is enabled and the oneof field contains a static sub-message, an attacker can use this flaw to leak memory potentially resulting in a denial of service. The highest threat from this vulnerability is to system availability.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","source":"CVE-2020-26243"},{"type":"Red Hat","score":"Important","source":"CVE-2020-26243"}],"affected":[{"ecosystem":"Red Hat:service_mesh:1","package":"servicemesh-proxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"provider":"redhat-vex","source":"CVE-2020-26243","relation":"self"}],"product_status":[{"vendor":"Red Hat","product":"OpenShift Service Mesh 1","cpe":"cpe:/a:redhat:service_mesh:1","status":"affected","packages":["servicemesh-proxy"],"package_count":1,"fixed":[],"advisories":[],"note":"Will not fix","provider":"redhat-vex","source":"CVE-2020-26243"}],"references":[{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2020/cve-2020-26243.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2020-26243"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=1902065"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2020-26243"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-26243"},{"type":"WEB","url":"https://github.com/nanopb/nanopb/security/advisories/GHSA-85rr-4rh9-hhwh"}]}],"references":[{"type":"WEB","url":"https://github.com/nanopb/nanopb/security/advisories/GHSA-85rr-4rh9-hhwh"},{"type":"WEB","url":"https://github.com/nanopb/nanopb/issues/615"},{"type":"WEB","url":"https://github.com/nanopb/nanopb/commit/4fe23595732b6f1254cfc11a9b8d6da900b55b0c"},{"type":"WEB","url":"https://github.com/nanopb/nanopb/blob/2b48a361786dfb1f63d229840217a93aae064667/CHANGELOG.txt"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2020-26243"},{"type":"WEB","url":"https://www.suse.com/support/security/rating/"},{"type":"ADVISORY","url":"https://security-tracker.debian.org/tracker/CVE-2020-26243"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-26243"},{"type":"PACKAGE","url":"https://pypi.org/project/nanopb"},{"type":"ADVISORY","url":"https://github.com/advisories/GHSA-85rr-4rh9-hhwh"},{"type":"REPORT","url":"https://ubuntu.com/security/CVE-2020-26243"},{"type":"REPORT","url":"https://github.com/nanopb/nanopb/commit/edf6dcbffee4d614ac0c2c1b258ab95185bdb6e9"},{"type":"ADVISORY","url":"https://ubuntu.com/security/notices/USN-6121-1"},{"type":"REPORT","url":"https://www.cve.org/CVERecord?id=CVE-2020-26243"},{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2020/cve-2020-26243.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2020-26243"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=1902065"}],"sources":[{"provider":"csaf-suse","source_id":"openSUSE-SU-2024:11074-1","url":"https://www.suse.com/security/cve/CVE-2020-26243/","license":"TLP:CLEAR, mirroring permitted","modified_at":"2024-06-15T00:00:00Z","relation":"upstream"},{"provider":"osv","source_id":"USN-6121-1","url":"https://osv.dev/vulnerability/USN-6121-1","license":"CC-BY-SA-4.0","modified_at":"2026-04-22T10:35:16.428853Z","relation":"upstream"},{"provider":"osv","source_id":"openSUSE-SU-2024:11074-1","url":"https://osv.dev/vulnerability/openSUSE-SU-2024:11074-1","modified_at":"2026-02-04T02:52:40.75074Z","relation":"upstream"},{"provider":"cvelistv5","source_id":"CVE-2020-26243","url":"https://www.cve.org/CVERecord?id=CVE-2020-26243","license":"CC-BY-4.0","modified_at":"2024-08-04T15:56:04.801Z","relation":"self"},{"provider":"csaf-suse","source_id":"CVE-2020-26243","url":"https://www.suse.com/security/cve/CVE-2020-26243/","license":"TLP:CLEAR, mirroring permitted","modified_at":"2025-03-15T09:38:38Z","relation":"self"},{"provider":"nvd","source_id":"CVE-2020-26243","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-26243","relation":"self"},{"provider":"osv","source_id":"DEBIAN-CVE-2020-26243","url":"https://osv.dev/vulnerability/DEBIAN-CVE-2020-26243","modified_at":"2026-10-26T12:01:06.842268Z","relation":"self"},{"provider":"osv","source_id":"GHSA-85rr-4rh9-hhwh","url":"https://osv.dev/vulnerability/GHSA-85rr-4rh9-hhwh","license":"CC-BY-4.0","modified_at":"2026-07-08T06:00:09.403204Z","relation":"self"},{"provider":"osv","source_id":"PYSEC-2026-684","url":"https://osv.dev/vulnerability/PYSEC-2026-684","license":"CC-BY-4.0","modified_at":"2026-07-06T08:00:39.967579Z","relation":"self"},{"provider":"osv","source_id":"UBUNTU-CVE-2020-26243","url":"https://osv.dev/vulnerability/UBUNTU-CVE-2020-26243","license":"CC-BY-SA-4.0","modified_at":"2026-04-22T12:36:20.739465Z","relation":"self"},{"provider":"redhat-vex","source_id":"CVE-2020-26243","url":"https://access.redhat.com/security/cve/CVE-2020-26243","license":"CC-BY-4.0","modified_at":"2026-02-02T07:28:11.514562Z","relation":"self"}]}
