{"id":"CVE-2026-73492","aliases":["DEBIAN-CVE-2026-73492","EUVD-2026-57629","GHSA-5qhf-9phg-95m2","SUSE-SU-2026:24195-1","SUSE-SU-2026:24250-1","UBUNTU-CVE-2026-73492","openSUSE-SU-2026:12153-1","openSUSE-SU-2026:22068-1"],"status":"published","title":"Loofah `allowed_uri?` does not detect `javascript:` URIs split by numeric character references without semicolons","description":"Loofah is a general library for manipulating and transforming HTML/XML documents and fragments, built on top of Nokogiri. From 2.25.0 until 2.25.2, Loofah::HTML5::Scrub.allowed_uri? does not reject javascript: or vbscript: URIs whose scheme is split by semicolon-less numeric character references such as \u0026#58, \u0026#9, \u0026#10, or \u0026#13. CGI.unescapeHTML leaves these references encoded, so allowed_uri? reports the URL safe even though a browser decodes an encoded colon or strips encoded whitespace and executes the resulting URI scheme. This issue affects only callers that pass HTML-encoded strings directly to allowed_uri?; Loofah's default sanitize() path is not affected. This issue is fixed in version 2.25.2.","severity":{"version":"4.0","score":2.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","level":"low","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.00394,"percentile":0.34084,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-184","CWE-79"],"published":"2026-07-21T22:03:11Z","modified":"2026-10-28T02:30:53Z","fixes":[{"ecosystem":"RubyGems","package":"loofah","fixed_in":["2.25.2"],"sources":["ghsa","osv"]},{"ecosystem":"Debian:14","package":"ruby-loofah","fixed_in":["2.25.2-1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"RubyGems","package":"loofah","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.25.0"},{"fixed":"2.25.2"}]}]},{"source":"osv","ecosystem":"Debian:12","package":"ruby-loofah","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.19.1-1","2.20.0-1","2.21.3-1","2.21.4-1","2.22.0-1","2.24.0-1","2.24.1-1","2.25.0-1","2.25.1-1","2.25.1-2","2.25.2-1"]},{"source":"osv","ecosystem":"Debian:13","package":"ruby-loofah","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.24.0-1","2.24.1-1","2.25.0-1","2.25.1-1","2.25.1-2","2.25.2-1"]},{"source":"osv","ecosystem":"Debian:14","package":"ruby-loofah","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.25.2-1"}]}],"versions":["2.24.0-1","2.24.1-1","2.25.0-1","2.25.1-1","2.25.1-2"]},{"source":"osv","ecosystem":"RubyGems","package":"loofah","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.25.0"},{"fixed":"2.25.2"}]}],"versions":["2.25.0","2.25.1"]},{"source":"osv","ecosystem":"SUSE:Linux Enterprise High Availability Extension 16.0","package":"hawk2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.7.2+git.1788518533.7d4dadd6-160000.1.1"}]}],"bundled":7},{"source":"osv","ecosystem":"SUSE:Linux Enterprise Server for SAP applications 16.0","package":"hawk2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.7.2+git.1788518533.7d4dadd6-160000.1.1"}]}],"bundled":7},{"source":"osv","ecosystem":"Ubuntu:16.04:LTS","package":"ruby-loofah","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.0.2-1","2.0.3-1","2.0.3-2","2.0.3-2+deb9u1build0.16.04.1","2.0.3-2+deb9u2build0.16.04.1","2.0.3-2+deb9u3build0.16.04.1"]},{"source":"osv","ecosystem":"Ubuntu:18.04:LTS","package":"ruby-loofah","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.0.3-2","2.2.2-1"]},{"source":"osv","ecosystem":"Ubuntu:20.04:LTS","package":"ruby-loofah","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.2.3-1","2.3.1+dfsg-1","2.4.0+dfsg-1"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"ruby-loofah","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.12.0-1","2.13.0-1","2.13.0-2"]},{"source":"osv","ecosystem":"Ubuntu:24.04:LTS","package":"ruby-loofah","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.21.3-1","2.21.4-1","2.22.0-1"]},{"source":"osv","ecosystem":"Ubuntu:26.10","package":"ruby-loofah","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.25.0-1","2.25.1-2","2.25.2-1"]},{"source":"osv","ecosystem":"Ubuntu:26.04:LTS","package":"ruby-loofah","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"versions":["2.24.1-1","2.25.0-1"]},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"hawk2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.7.2+git.1792148770.648dcddb-1.1"}]}],"bundled":7},{"source":"osv","ecosystem":"openSUSE:Leap 16.0","package":"hawk2","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.7.2+git.1788518533.7d4dadd6-160000.1.1"}]}],"bundled":7}],"products":[{"vendor":"flavorjones","product":"loofah"}],"references":[{"url":"https://github.com/flavorjones/loofah/security/advisories/GHSA-5qhf-9phg-95m2","tags":["x_refsource_CONFIRM","advisory","web","report"]},{"url":"https://github.com/flavorjones/loofah/pull/308","tags":["x_refsource_MISC","fix","report"]},{"url":"https://github.com/flavorjones/loofah/commit/f1be9d893b5a8dd79240441a912d8897e74c38c0","tags":["x_refsource_MISC","fix","web","report"]},{"url":"https://github.com/flavorjones/loofah/releases/tag/v2.25.2","tags":["x_refsource_MISC","web","report"]},{"url":"https://github.com/advisories/GHSA-5qhf-9phg-95m2"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/73xxx/CVE-2026-73492.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-73492","tags":["advisory"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2026-73492","tags":["advisory"]},{"url":"https://github.com/flavorjones/loofah","tags":["package"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202624195-1/","tags":["advisory"]},{"url":"https://bugzilla.suse.com/1268996","tags":["report"]},{"url":"https://bugzilla.suse.com/1273348","tags":["report"]},{"url":"https://bugzilla.suse.com/1274860","tags":["report"]},{"url":"https://bugzilla.suse.com/1275019","tags":["report"]},{"url":"https://bugzilla.suse.com/1275179","tags":["report"]},{"url":"https://bugzilla.suse.com/1275183","tags":["report"]},{"url":"https://bugzilla.suse.com/1275188","tags":["report"]},{"url":"https://bugzilla.suse.com/1275200","tags":["report"]},{"url":"https://bugzilla.suse.com/1275213","tags":["report"]},{"url":"https://www.suse.com/security/cve/CVE-2026-42246","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-66066","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-71847","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73490","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73491","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73492","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-73648","tags":["web"]},{"url":"https://www.suse.com/support/update/announcement/2026/suse-su-202624250-1/","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2026-73492","tags":["report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-73492","tags":["report"]},{"url":"","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2026-73492","title":"Loofah `allowed_uri?` does not detect `javascript:` URIs split by numeric character references without semicolons","description":"Loofah is a general library for manipulating and transforming HTML/XML documents and fragments, built on top of Nokogiri. From 2.25.0 until 2.25.2, Loofah::HTML5::Scrub.allowed_uri? does not reject javascript: or vbscript: URIs whose scheme is split by semicolon-less numeric character references such as \u0026#58, \u0026#9, \u0026#10, or \u0026#13. CGI.unescapeHTML leaves these references encoded, so allowed_uri? reports the URL safe even though a browser decodes an encoded colon or strips encoded whitespace and executes the resulting URI scheme. This issue affects only callers that pass HTML-encoded strings directly to allowed_uri?; Loofah's default sanitize() path is not affected. This issue is fixed in version 2.25.2.","status":"published","published":"2026-08-12T21:00:24.679Z","modified":"2026-08-14T22:18:10.839Z","cvss":[{"version":"4.0","score":2.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","level":"low","assessor":"cna"}],"cwes":["CWE-79","CWE-184"],"updated_at":"2026-11-02T13:43:33.766176Z"}],"euvd":[{"id":"EUVD-2026-57629","description":"Loofah is a general library for manipulating and transforming HTML/XML documents and fragments, built on top of Nokogiri. From 2.25.0 until 2.25.2, Loofah::HTML5::Scrub.allowed_uri? does not reject javascript: or vbscript: URIs whose scheme is split by semicolon-less numeric character references such as \u0026#58, \u0026#9, \u0026#10, or \u0026#13. CGI.unescapeHTML leaves these references encoded, so allowed_uri? reports the URL safe even though a browser decodes an encoded colon or strips encoded whitespace and executes the resulting URI scheme. This issue affects only callers that pass HTML-encoded strings directly to allowed_uri?; Loofah's default sanitize() path is not affected. This issue is fixed in version 2.25.2.","status":"published","published":"2026-08-12T21:00:24Z","modified":"2026-08-14T22:18:10Z","cvss":[{"version":"4.0","score":2.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","level":"low"}],"updated_at":"2026-11-02T18:01:53.008072Z"}],"ghsa":[{"id":"GHSA-5qhf-9phg-95m2","title":"Loofah `allowed_uri?` does not detect `javascript:` URIs split by numeric character references without semicolons","description":"## Summary\n\n`Loofah::HTML5::Scrub.allowed_uri?` does not correctly reject `javascript:` or `vbscript:` URIs when the scheme is split by a numeric character reference that has no trailing semicolon. A browser decodes such references and resolves the URL to an executable `javascript:` scheme, while `allowed_uri?` reports it safe.\n\nThis is a bypass of the fix for [GHSA-46fp-8f5p-pf2m](https://github.com/flavorjones/loofah/security/advisories/GHSA-46fp-8f5p-pf2m), which handled numeric character references with a trailing `;` (`\u0026#9;`, `\u0026#10;`, `\u0026#13;`) but did not cover the forms without semicolons.\n\n## Details\n\n`allowed_uri?` decodes HTML entities with `CGI.unescapeHTML`, which decodes numeric character references only when they carry a trailing `;`. A reference without a semicolon such as `\u0026#58` (colon) or `\u0026#9` (tab) is left literal, so the scheme-detection check finds no scheme, and the method falls through to its scheme-less path and returns `true`.\n\nA browser, however, decodes numeric character references even without a trailing semicolon. An encoded colon such as `\u0026#58` becomes the `:` scheme separator, so `javascript\u0026#58alert(1)` resolves to `javascript:alert(1)`. Encoded whitespace such as `\u0026#9` (tab) is decoded and then stripped from the URL, rejoining the surrounding text, so `java\u0026#9script:alert(1)` also resolves to `javascript:alert(1)`. In both cases the URL executes while `allowed_uri?` approved it as safe.\n\nNote that Loofah's default `sanitize()` path is **not** affected, because Nokogiri decodes or entity-escapes HTML entities during parsing before Loofah evaluates the URI protocol. This issue only affects callers of the public `allowed_uri?` string-level helper that pass it HTML-encoded strings.\n\n## Impact\n\nCallers that validate a user-controlled URL with `Loofah::HTML5::Scrub.allowed_uri?` and then render the approved value into an `href` or other browser-interpreted URI attribute may be vulnerable to cross-site scripting (XSS). This includes applications that call `allowed_uri?` directly, as well as higher-level features built on top of it, such as Action Text 8.2's markdown link validation.\n\n## Mitigation\n\nUpgrade to Loofah \u003e= 2.25.2.\n\n## Credit\n\nResponsibly reported by GitHub user @MoonFuji.","status":"published","published":"2026-07-21T22:03:11Z","modified":"2026-07-21T22:03:13Z","cvss":[{"version":"4.0","score":2.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","level":"low"}],"cwes":["CWE-79","CWE-184"],"updated_at":"2026-11-02T14:40:50.444681Z"}],"nvd":[{"id":"CVE-2026-73492","description":"Loofah is a general library for manipulating and transforming HTML/XML documents and fragments, built on top of Nokogiri. From 2.25.0 until 2.25.2, Loofah::HTML5::Scrub.allowed_uri? does not reject javascript: or vbscript: URIs whose scheme is split by semicolon-less numeric character references such as \u0026#58, \u0026#9, \u0026#10, or \u0026#13. CGI.unescapeHTML leaves these references encoded, so allowed_uri? reports the URL safe even though a browser decodes an encoded colon or strips encoded whitespace and executes the resulting URI scheme. This issue affects only callers that pass HTML-encoded strings directly to allowed_uri?; Loofah's default sanitize() path is not affected. This issue is fixed in version 2.25.2.","status":"published","published":"2026-08-12T22:17:16.527Z","modified":"2026-10-24T15:10:00.19Z","cvss":[{"version":"4.0","score":2.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"low","assessor":"secondary"}],"cwes":["CWE-79","CWE-184"],"updated_at":"2026-11-02T14:12:37.217486Z"}],"osv":[{"id":"CVE-2026-73492","title":"Loofah `allowed_uri?` does not detect `javascript:` URIs split by numeric character references without semicolons","description":"Loofah is a general library for manipulating and transforming HTML/XML documents and fragments, built on top of Nokogiri. From 2.25.0 until 2.25.2, Loofah::HTML5::Scrub.allowed_uri? does not reject javascript: or vbscript: URIs whose scheme is split by semicolon-less numeric character references such as \u0026#58, \u0026#9, \u0026#10, or \u0026#13. CGI.unescapeHTML leaves these references encoded, so allowed_uri? reports the URL safe even though a browser decodes an encoded colon or strips encoded whitespace and executes the resulting URI scheme. This issue affects only callers that pass HTML-encoded strings directly to allowed_uri?; Loofah's default sanitize() path is not affected. This issue is fixed in version 2.25.2.","status":"published","published":"2026-08-12T21:00:24.679Z","modified":"2026-10-28T02:30:53.361101918Z","cvss":[{"version":"4.0","score":2.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","level":"low"}],"cwes":["CWE-184","CWE-79"],"updated_at":"2026-11-02T15:45:16.365946Z"},{"id":"DEBIAN-CVE-2026-73492","description":"Loofah is a general library for manipulating and transforming HTML/XML documents and fragments, built on top of Nokogiri. From 2.25.0 until 2.25.2, Loofah::HTML5::Scrub.allowed_uri? does not reject javascript: or vbscript: URIs whose scheme is split by semicolon-less numeric character references such as \u0026#58, \u0026#9, \u0026#10, or \u0026#13. CGI.unescapeHTML leaves these references encoded, so allowed_uri? reports the URL safe even though a browser decodes an encoded colon or strips encoded whitespace and executes the resulting URI scheme. This issue affects only callers that pass HTML-encoded strings directly to allowed_uri?; Loofah's default sanitize() path is not affected. This issue is fixed in version 2.25.2.","status":"published","published":"2026-08-12T22:17:16.527Z","modified":"2026-10-25T09:47:31.663033333Z","cvss":[{"version":"4.0","score":2.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"low"}],"updated_at":"2026-11-02T15:46:02.499355Z"},{"id":"GHSA-5qhf-9phg-95m2","title":"Loofah `allowed_uri?` does not detect `javascript:` URIs split by numeric character references without semicolons","description":"## Summary\n\n`Loofah::HTML5::Scrub.allowed_uri?` does not correctly reject `javascript:` or `vbscript:` URIs when the scheme is split by a numeric character reference that has no trailing semicolon. A browser decodes such references and resolves the URL to an executable `javascript:` scheme, while `allowed_uri?` reports it safe.\n\nThis is a bypass of the fix for [GHSA-46fp-8f5p-pf2m](https://github.com/flavorjones/loofah/security/advisories/GHSA-46fp-8f5p-pf2m), which handled numeric character references with a trailing `;` (`\u0026#9;`, `\u0026#10;`, `\u0026#13;`) but did not cover the forms without semicolons.\n\n## Details\n\n`allowed_uri?` decodes HTML entities with `CGI.unescapeHTML`, which decodes numeric character references only when they carry a trailing `;`. A reference without a semicolon such as `\u0026#58` (colon) or `\u0026#9` (tab) is left literal, so the scheme-detection check finds no scheme, and the method falls through to its scheme-less path and returns `true`.\n\nA browser, however, decodes numeric character references even without a trailing semicolon. An encoded colon such as `\u0026#58` becomes the `:` scheme separator, so `javascript\u0026#58alert(1)` resolves to `javascript:alert(1)`. Encoded whitespace such as `\u0026#9` (tab) is decoded and then stripped from the URL, rejoining the surrounding text, so `java\u0026#9script:alert(1)` also resolves to `javascript:alert(1)`. In both cases the URL executes while `allowed_uri?` approved it as safe.\n\nNote that Loofah's default `sanitize()` path is **not** affected, because Nokogiri decodes or entity-escapes HTML entities during parsing before Loofah evaluates the URI protocol. This issue only affects callers of the public `allowed_uri?` string-level helper that pass it HTML-encoded strings.\n\n## Impact\n\nCallers that validate a user-controlled URL with `Loofah::HTML5::Scrub.allowed_uri?` and then render the approved value into an `href` or other browser-interpreted URI attribute may be vulnerable to cross-site scripting (XSS). This includes applications that call `allowed_uri?` directly, as well as higher-level features built on top of it, such as Action Text 8.2's markdown link validation.\n\n## Mitigation\n\nUpgrade to Loofah \u003e= 2.25.2.\n\n## Credit\n\nResponsibly reported by GitHub user @MoonFuji.","status":"published","published":"2026-07-21T22:03:11Z","modified":"2026-09-10T03:51:10.544951806Z","cvss":[{"version":"4.0","score":2.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","level":"low"}],"cwes":["CWE-184","CWE-79"],"updated_at":"2026-11-02T15:46:38.553953Z"},{"id":"UBUNTU-CVE-2026-73492","description":"Loofah is a general library for manipulating and transforming HTML/XML documents and fragments, built on top of Nokogiri. From 2.25.0 until 2.25.2, Loofah::HTML5::Scrub.allowed_uri? does not reject javascript: or vbscript: URIs whose scheme is split by semicolon-less numeric character references such as \u0026#58, \u0026#9, \u0026#10, or \u0026#13. CGI.unescapeHTML leaves these references encoded, so allowed_uri? reports the URL safe even though a browser decodes an encoded colon or strips encoded whitespace and executes the resulting URI scheme. This issue affects only callers that pass HTML-encoded strings directly to allowed_uri?; Loofah's default sanitize() path is not affected. This issue is fixed in version 2.25.2.","status":"published","published":"2026-08-12T22:17:00Z","modified":"2026-10-17T13:01:03.398982484Z","cvss":[{"version":"4.0","score":2.3,"vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","level":"low"}],"updated_at":"2026-11-02T16:57:08.628462Z"},{"id":"openSUSE-SU-2026:12153-1","title":"hawk2-2.7.2+git.1792148770.648dcddb-1.1 on GA media","description":"These are all security issues fixed in the hawk2-2.7.2+git.1792148770.648dcddb-1.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2026-10-16T00:00:00Z","modified":"2026-10-17T10:00:04.120583882Z","updated_at":"2026-11-02T16:58:40.245664Z"},{"id":"openSUSE-SU-2026:22068-1","title":"Security update for hawk2","description":"This update for hawk2 fixes the following issues:\n\n- CVE-2026-42246: net-imap: MITM attacker can cause Net::IMAP#starttls to return successfully, without starting TLS\n  (bsc#1268996).\n- CVE-2026-66066: unsafe image processing operations on untrusted uploads can allow arbitrary file reading and remote\n  code execution (bsc#1273348).\n- CVE-2026-71847: json: heap use-after free in JSON::ResumableParser partial_value can lead to crash on truncated\n  duplicate-key streams (bsc#1275213).\n- CVE-2026-73490: loofah: improper handling of SVG attributes in the HTML5 sanitizer allows bypass of local-reference\n  restrictions (bsc#1275179).\n- CVE-2026-73491: loofah: improper handling of javascript: URIs can lead to XSS (bsc#1275183).\n- CVE-2026-73492: loofah: improper handling of javascript: and vbscript: URIs can lead to XSS (bsc#1275188).\n- CVE-2026-73648: rails-html-sanitizer: cross-site scripting is possible when the sanitizer is configured to allow\n  certain SVG reference elements (bsc#1275200).\n\nChanges for hawk2:\n\n- Update to version 2.7.2+git.1788518533.7d4dadd6 (bsc#1275019):\n * Test: give sle15 more time when choosing between sle15 and sle16\n * Dev: bump jQuery version to 4.0.0\n * Dev: bump jQuery version to 3.5.0\n * Dev: bump jQuery version to 2.2.4\n * Test: update the e2e test for the change allowing custom parameters\n * Dev: enable custom Parameters and Meta Attributes (bsc#1274860)\n * CI/CD: update hawk examiner entry point\n * Test: enable test_add_clone against hawk-apiserver verion 0.2.1\n * Test: fix SyntaxWarning: invalid escape sequence '\\|'\n * Test: make the tests compatible against hawk-apiserver ver0.2.0\n","status":"published","published":"2026-10-09T10:01:26Z","modified":"2026-10-19T17:23:11.651310245Z","updated_at":"2026-11-02T16:58:42.426393Z"},{"id":"SUSE-SU-2026:24195-1","title":"Security update for hawk2","description":"This update for hawk2 fixes the following issues:\n\n- CVE-2026-42246: net-imap: MITM attacker can cause Net::IMAP#starttls to return successfully, without starting TLS\n  (bsc#1268996).\n- CVE-2026-66066: unsafe image processing operations on untrusted uploads can allow arbitrary file reading and remote\n  code execution (bsc#1273348).\n- CVE-2026-71847: json: heap use-after free in JSON::ResumableParser partial_value can lead to crash on truncated\n  duplicate-key streams (bsc#1275213).\n- CVE-2026-73490: loofah: improper handling of SVG attributes in the HTML5 sanitizer allows bypass of local-reference\n  restrictions (bsc#1275179).\n- CVE-2026-73491: loofah: improper handling of javascript: URIs can lead to XSS (bsc#1275183).\n- CVE-2026-73492: loofah: improper handling of javascript: and vbscript: URIs can lead to XSS (bsc#1275188).\n- CVE-2026-73648: rails-html-sanitizer: cross-site scripting is possible when the sanitizer is configured to allow\n  certain SVG reference elements (bsc#1275200).\n\nChanges for hawk2:\n\n- Update to version 2.7.2+git.1788518533.7d4dadd6 (bsc#1275019):\n * Test: give sle15 more time when choosing between sle15 and sle16\n * Dev: bump jQuery version to 4.0.0\n * Dev: bump jQuery version to 3.5.0\n * Dev: bump jQuery version to 2.2.4\n * Test: update the e2e test for the change allowing custom parameters\n * Dev: enable custom Parameters and Meta Attributes (bsc#1274860)\n * CI/CD: update hawk examiner entry point\n * Test: enable test_add_clone against hawk-apiserver verion 0.2.1\n * Test: fix SyntaxWarning: invalid escape sequence '\\|'\n * Test: make the tests compatible against hawk-apiserver ver0.2.0\n","status":"published","published":"2026-10-09T10:11:39Z","modified":"2026-10-21T17:23:09.534601518Z","updated_at":"2026-11-02T15:54:04.519245Z"},{"id":"SUSE-SU-2026:24250-1","title":"Security update for hawk2","description":"This update for hawk2 fixes the following issues:\n\n- CVE-2026-42246: net-imap: MITM attacker can cause Net::IMAP#starttls to return successfully, without starting TLS\n  (bsc#1268996).\n- CVE-2026-66066: unsafe image processing operations on untrusted uploads can allow arbitrary file reading and remote\n  code execution (bsc#1273348).\n- CVE-2026-71847: json: heap use-after free in JSON::ResumableParser partial_value can lead to crash on truncated\n  duplicate-key streams (bsc#1275213).\n- CVE-2026-73490: loofah: improper handling of SVG attributes in the HTML5 sanitizer allows bypass of local-reference\n  restrictions (bsc#1275179).\n- CVE-2026-73491: loofah: improper handling of javascript: URIs can lead to XSS (bsc#1275183).\n- CVE-2026-73492: loofah: improper handling of javascript: and vbscript: URIs can lead to XSS (bsc#1275188).\n- CVE-2026-73648: rails-html-sanitizer: cross-site scripting is possible when the sanitizer is configured to allow\n  certain SVG reference elements (bsc#1275200).\n\nChanges for hawk2:\n\n- Update to version 2.7.2+git.1788518533.7d4dadd6 (bsc#1275019):\n * Test: give sle15 more time when choosing between sle15 and sle16\n * Dev: bump jQuery version to 4.0.0\n * Dev: bump jQuery version to 3.5.0\n * Dev: bump jQuery version to 2.2.4\n * Test: update the e2e test for the change allowing custom parameters\n * Dev: enable custom Parameters and Meta Attributes (bsc#1274860)\n * CI/CD: update hawk examiner entry point\n * Test: enable test_add_clone against hawk-apiserver verion 0.2.1\n * Test: fix SyntaxWarning: invalid escape sequence '\\|'\n * Test: make the tests compatible against hawk-apiserver ver0.2.0\n","status":"published","published":"2026-10-09T10:10:52Z","modified":"2026-10-21T17:23:12.551796041Z","updated_at":"2026-11-02T15:54:04.519245Z"}]}}