{"id":"CVE-2026-115897","aliases":["AZL-111404","CLSA-2026-1793098798","CLSA-2026-1793099227","CLSA-2026-1793125688","CLSA-2026-1793180818","CLSA-2026-1793183866","CLSA-2026-1793187934","CLSA-2026-1793207115","CLSA-2026-1793209309","CLSA-2026-1793789998","CLSA-2026-1793790235","EUVD-2026-109190","GHSA-5c6j-r48x-rmvq","GHSA-m5mm-p8h7-m29v","openSUSE-SU-2026:12424-1"],"status":"published","title":"Serialize JavaScript: Cross-site scripting (XSS) via unescaped \u003c/script at the end of a serialized function body","description":"Serialize JavaScript serializes JavaScript values to a superset of JSON that includes regular expressions and functions. Prior to 7.1.3, the function-source escaping logic does not neutralize a bare closing-script prefix when attacker-influenced function source text ends exactly at that prefix. Because each function body is escaped independently, a delimiter supplied by surrounding serialized output can terminate an HTML script element, and a later serialized value supplies injected markup that becomes a live element in the page. Exploitation requires control of a serialized function's source text, such as through a spoofed toString(). This issue is fixed in version 7.1.3.","severity":{"version":"4.0","score":2.1,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","level":"low","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-12","score":0.00307,"percentile":0.23776,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-79"],"published":"2026-10-23T13:20:43.932Z","modified":"2026-11-06T17:27:18Z","fixes":[{"ecosystem":"npm","package":"serialize-javascript","fixed_in":["7.1.3"],"sources":["ghsa"]},{"ecosystem":"TuxCare:npm","package":"serialize-javascript","fixed_in":["6.0.1-tuxcare.1","6.0.0-tuxcare.1","5.0.1-tuxcare.3","3.1.0-tuxcare.2","2.1.2-tuxcare.2","7.0.7-tuxcare.1"],"sources":["osv"]}],"affected":[{"source":"ghsa","ecosystem":"npm","package":"serialize-javascript","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"7.1.3"}]}]},{"source":"osv","ecosystem":"Azure Linux:3","package":"python-tensorboard","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"2.16.2-6"}]}]},{"source":"osv","ecosystem":"TuxCare:npm","package":"serialize-javascript","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"7.1.2-tuxcare.0"},{"fixed":"7.1.2-tuxcare.1"}]}],"versions":["7.1.2"],"bundled":2},{"source":"osv","ecosystem":"TuxCare:npm","package":"serialize-javascript","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.0.2-tuxcare.0"},{"fixed":"6.0.2-tuxcare.3"}]}],"versions":["6.0.2","6.0.2-tuxcare.1","6.0.2-tuxcare.2"],"bundled":2},{"source":"osv","ecosystem":"TuxCare:npm","package":"serialize-javascript","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"7.1.1-tuxcare.0"},{"fixed":"7.1.1-tuxcare.2"}]}],"versions":["7.1.1","7.1.1-tuxcare.1"],"bundled":2},{"source":"osv","ecosystem":"TuxCare:npm","package":"serialize-javascript","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.0.1-tuxcare.0"},{"fixed":"6.0.1-tuxcare.1"}]}],"versions":["6.0.1"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"serialize-javascript","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"6.0.0-tuxcare.0"},{"fixed":"6.0.0-tuxcare.1"}]}],"versions":["6.0.0"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"serialize-javascript","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"5.0.1-tuxcare.0"},{"fixed":"5.0.1-tuxcare.3"}]}],"versions":["5.0.1","5.0.1-tuxcare.1","5.0.1-tuxcare.2"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"serialize-javascript","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.1.0-tuxcare.0"},{"fixed":"3.1.0-tuxcare.2"}]}],"versions":["3.1.0","3.1.0-tuxcare.1"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"serialize-javascript","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.1.2-tuxcare.0"},{"fixed":"2.1.2-tuxcare.2"}]}],"versions":["2.1.2","2.1.2-tuxcare.1"]},{"source":"osv","ecosystem":"TuxCare:npm","package":"serialize-javascript","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0-tuxcare.0"},{"fixed":"3.0.0-tuxcare.1"}]}],"versions":["3.0.0"],"bundled":2},{"source":"osv","ecosystem":"TuxCare:npm","package":"serialize-javascript","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"7.0.7-tuxcare.0"},{"fixed":"7.0.7-tuxcare.1"}]}],"versions":["7.0.7"]},{"source":"osv","ecosystem":"npm","package":"serialize-javascript","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"7.1.3"}]}],"bundled":2},{"source":"osv","ecosystem":"openSUSE:Tumbleweed","package":"agama-web-ui","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"25+475.275dd4727-56.1"}]}],"bundled":11}],"products":[{"vendor":"yahoo","product":"serialize-javascript"}],"references":[{"url":"https://github.com/yahoo/serialize-javascript/security/advisories/GHSA-m5mm-p8h7-m29v","tags":["x_refsource_CONFIRM","advisory","web"]},{"url":"https://github.com/yahoo/serialize-javascript/pull/235","tags":["x_refsource_MISC","fix","web"]},{"url":"https://github.com/yahoo/serialize-javascript/commit/2864b3c6260a3bfd52d2db3e70d1a079de108a61","tags":["x_refsource_MISC","fix","web"]},{"url":"https://github.com/yahoo/serialize-javascript/releases/tag/v7.1.3","tags":["x_refsource_MISC","advisory","web"]},{"url":"https://github.com/advisories/GHSA-m5mm-p8h7-m29v"},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-115897","tags":["web","advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/115xxx/CVE-2026-115754.json","tags":["advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-115754","tags":["advisory"]},{"url":"https://www.vulncheck.com/advisories/serialize-javascript-7.0.1-before-7.1.3-xss-via-unescaped-script-in-function-body","tags":["advisory"]},{"url":"https://github.com/yahoo/serialize-javascript","tags":["package"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/115xxx/CVE-2026-115897.json","tags":["advisory"]},{"url":"","tags":["advisory"]},{"url":"https://www.suse.com/security/cve/CVE-2026-102277","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-110725","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-111181","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-111755","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-111756","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-115754","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-115897","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-116689","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-75899","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-84369","tags":["web"]},{"url":"https://www.suse.com/security/cve/CVE-2026-86472","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2026-115897","title":"Serialize JavaScript: Cross-site scripting (XSS) via unescaped \u003c/script at the end of a serialized function body","description":"Serialize JavaScript serializes JavaScript values to a superset of JSON that includes regular expressions and functions. Prior to 7.1.3, the function-source escaping logic does not neutralize a bare closing-script prefix when attacker-influenced function source text ends exactly at that prefix. Because each function body is escaped independently, a delimiter supplied by surrounding serialized output can terminate an HTML script element, and a later serialized value supplies injected markup that becomes a live element in the page. Exploitation requires control of a serialized function's source text, such as through a spoofed toString(). This issue is fixed in version 7.1.3.","status":"published","published":"2026-10-23T21:37:41.097Z","modified":"2026-10-26T17:41:50.594Z","cvss":[{"version":"4.0","score":2.1,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","level":"low","assessor":"cna"}],"cwes":["CWE-79"],"updated_at":"2026-11-02T14:20:01.618694Z"}],"euvd":[{"id":"EUVD-2026-109190","description":"Serialize JavaScript serializes JavaScript values to a superset of JSON that includes regular expressions and functions. Prior to 7.1.3, the function-source escaping logic does not neutralize a bare closing-script prefix when attacker-influenced function source text ends exactly at that prefix. Because each function body is escaped independently, a delimiter supplied by surrounding serialized output can terminate an HTML script element, and a later serialized value supplies injected markup that becomes a live element in the page. Exploitation requires control of a serialized function's source text, such as through a spoofed toString(). This issue is fixed in version 7.1.3.","status":"published","published":"2026-10-23T21:37:41Z","modified":"2026-10-26T17:41:50Z","cvss":[{"version":"4.0","score":2.1,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","level":"low"}],"updated_at":"2026-11-02T16:59:28.784227Z"}],"ghsa":[{"id":"GHSA-m5mm-p8h7-m29v","title":"Serialize JavaScript: Cross-site scripting (XSS) via unescaped \u003c/script at the end of a serialized function body","description":"### Impact\n\n`serialize-javascript` escapes its output so it is safe to embed inside a\n`\u003cscript\u003e` element. Before 7.1.3 that guarantee did not hold for a **function\nvalue whose source ends in a bare `\u003c/script`**.\n\nEach function body is escaped on its own, and a bare `\u003c/script` was only\nneutralized when followed — within the same body — by a character the HTML\ntokenizer treats as ending the tag name (TAB, LF, FF, CR, SPACE, `/` or `\u003e`).\nA body ending exactly at `\u003c/script` has no following character, so it was\nemitted unescaped. The delimiter is then supplied by the surrounding output\n(for example the newline the `space` option emits after the value), and a\nlater serialized value can supply the closing `\u003e` followed by markup:\n\n```js\nconst serialize = require('serialize-javascript');\nfunction f() {} f.toString = () =\u003e 'function f(){ return 1 }//\u003c/script';\nfunction g() {} g.toString = () =\u003e 'function g(x){ return x } \u003e \u003cimg src=x onerror=alert(1)\u003e';\nserialize({ a: { f }, g }, { space: 2 });\n// {\n//   \"a\": {\n//     \"f\": function f(){ return 1 }//\u003c/script\n//   },\n//   \"g\": function g(x){ return x } \u003e \u003cimg src=x onerror=alert(1)\u003e\n// }\n```\n\nEmbedded in a `\u003cscript\u003e` element, the script ends at the injected tag and the\n`\u003cimg\u003e` becomes a live element in the page.\n\nExploitation requires an attacker to control the **source text** of a\nserialized function, in practice through a spoofed `toString()`. Real\nfunctions always end in `}`, so ordinary function values are not affected,\nand non-function values (including strings containing `\u003c/script`) are\nescaped correctly.\n\n### Patches\n\nFixed in **7.1.3** (#235). The bare `\u003c/script` form is now also matched at\nthe end of the function body, so it is escaped regardless of what follows it\nin the output.\n\n### Workarounds\n\nUpgrade to **7.1.3**. If you cannot upgrade, do not serialize function values\nwhose source text (or `toString()`) can be influenced by an attacker.\n\n### Credits\n\nReported by **ha_kr25** via the Yahoo bug bounty program.","status":"published","published":"2026-10-23T22:09:52Z","modified":"2026-10-23T22:09:53Z","cvss":[{"version":"4.0","score":2.1,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","level":"low"}],"cwes":["CWE-79"],"updated_at":"2026-11-02T14:41:35.723785Z"}],"nvd":[{"id":"CVE-2026-115897","description":"Serialize JavaScript serializes JavaScript values to a superset of JSON that includes regular expressions and functions. Prior to 7.1.3, the function-source escaping logic does not neutralize a bare closing-script prefix when attacker-influenced function source text ends exactly at that prefix. Because each function body is escaped independently, a delimiter supplied by surrounding serialized output can terminate an HTML script element, and a later serialized value supplies injected markup that becomes a live element in the page. Exploitation requires control of a serialized function's source text, such as through a spoofed toString(). This issue is fixed in version 7.1.3.","status":"published","published":"2026-10-23T22:16:59.153Z","modified":"2026-10-26T18:39:42.503Z","cvss":[{"version":"4.0","score":2.1,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:L/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"],"updated_at":"2026-11-02T14:13:03.126833Z"}],"osv":[{"id":"CVE-2026-115754","title":"serialize-javascript 7.0.1 before 7.1.3 XSS via unescaped \u003c/script in function body","description":"serialize-javascript from 7.0.1 before 7.1.3 contains a cross-site scripting vulnerability that allows attackers to break out of HTML script elements by ending serialized function source text with an unescaped \u003c/script. Attackers controlling a function's source via a spoofed toString() can combine surrounding output delimiters and later values to inject live markup such as img onerror handlers.","status":"published","published":"2026-10-23T13:20:43.932Z","modified":"2026-11-06T17:27:17.05848065Z","cvss":[{"version":"4.0","score":2.3,"vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","level":"low"}],"cwes":["CWE-79"],"updated_at":"2026-11-06T18:03:55.607917Z"},{"id":"CVE-2026-115897","title":"Serialize JavaScript: Cross-site scripting (XSS) via unescaped \u003c/script at the end of a serialized function body","description":"Serialize JavaScript serializes JavaScript values to a superset of JSON that includes regular expressions and functions. Prior to 7.1.3, the function-source escaping logic does not neutralize a bare closing-script prefix when attacker-influenced function source text ends exactly at that prefix. Because each function body is escaped independently, a delimiter supplied by surrounding serialized output can terminate an HTML script element, and a later serialized value supplies injected markup that becomes a live element in the page. Exploitation requires control of a serialized function's source text, such as through a spoofed toString(). This issue is fixed in version 7.1.3.","status":"published","published":"2026-10-23T21:37:41.097Z","modified":"2026-11-06T17:27:18.400576963Z","cvss":[{"version":"4.0","score":2.1,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","level":"low"}],"cwes":["CWE-79"],"updated_at":"2026-11-06T18:03:40.601771Z"},{"id":"GHSA-m5mm-p8h7-m29v","title":"Serialize JavaScript: Cross-site scripting (XSS) via unescaped \u003c/script at the end of a serialized function body","description":"### Impact\n\n`serialize-javascript` escapes its output so it is safe to embed inside a\n`\u003cscript\u003e` element. Before 7.1.3 that guarantee did not hold for a **function\nvalue whose source ends in a bare `\u003c/script`**.\n\nEach function body is escaped on its own, and a bare `\u003c/script` was only\nneutralized when followed — within the same body — by a character the HTML\ntokenizer treats as ending the tag name (TAB, LF, FF, CR, SPACE, `/` or `\u003e`).\nA body ending exactly at `\u003c/script` has no following character, so it was\nemitted unescaped. The delimiter is then supplied by the surrounding output\n(for example the newline the `space` option emits after the value), and a\nlater serialized value can supply the closing `\u003e` followed by markup:\n\n```js\nconst serialize = require('serialize-javascript');\nfunction f() {} f.toString = () =\u003e 'function f(){ return 1 }//\u003c/script';\nfunction g() {} g.toString = () =\u003e 'function g(x){ return x } \u003e \u003cimg src=x onerror=alert(1)\u003e';\nserialize({ a: { f }, g }, { space: 2 });\n// {\n//   \"a\": {\n//     \"f\": function f(){ return 1 }//\u003c/script\n//   },\n//   \"g\": function g(x){ return x } \u003e \u003cimg src=x onerror=alert(1)\u003e\n// }\n```\n\nEmbedded in a `\u003cscript\u003e` element, the script ends at the injected tag and the\n`\u003cimg\u003e` becomes a live element in the page.\n\nExploitation requires an attacker to control the **source text** of a\nserialized function, in practice through a spoofed `toString()`. Real\nfunctions always end in `}`, so ordinary function values are not affected,\nand non-function values (including strings containing `\u003c/script`) are\nescaped correctly.\n\n### Patches\n\nFixed in **7.1.3** (#235). The bare `\u003c/script` form is now also matched at\nthe end of the function body, so it is escaped regardless of what follows it\nin the output.\n\n### Workarounds\n\nUpgrade to **7.1.3**. If you cannot upgrade, do not serialize function values\nwhose source text (or `toString()`) can be influenced by an attacker.\n\n### Credits\n\nReported by **ha_kr25** via the Yahoo bug bounty program.","status":"published","published":"2026-10-23T22:09:52Z","modified":"2026-10-24T02:55:55.507718062Z","cvss":[{"version":"4.0","score":2.1,"vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N","level":"low"}],"cwes":["CWE-79"],"updated_at":"2026-11-02T15:46:51.463834Z"},{"id":"AZL-111404","title":"CVE-2026-115897 affecting package python-tensorboard 2.16.2-6","description":"Serialize JavaScript serializes JavaScript values to a superset of JSON that includes regular expressions and functions. Prior to 7.1.3, the function-source escaping logic does not neutralize a bare closing-script prefix when attacker-influenced function source text ends exactly at that prefix. Because each function body is escaped independently, a delimiter supplied by surrounding serialized output can terminate an HTML script element, and a later serialized value supplies injected markup that becomes a live element in the page. Exploitation requires control of a serialized function's source text, such as through a spoofed toString(). This issue is fixed in version 7.1.3.","status":"published","published":"2026-10-23T22:16:59Z","modified":"2026-11-03T05:33:06Z","updated_at":"2026-11-05T16:41:18.705965Z"},{"id":"CLSA-2026-1793098798","title":"TuxCare security update for serialize-javascript (2 CVEs)","description":"TuxCare rebuilt serialize-javascript to address 2 CVEs. Fixed in 7.1.2-tuxcare.1.","status":"published","published":"2026-10-27T10:59:58Z","modified":"2026-10-27T13:30:09.762639302Z","updated_at":"2026-11-02T15:43:55.34846Z"},{"id":"CLSA-2026-1793099227","title":"TuxCare security update for serialize-javascript (2 CVEs)","description":"TuxCare rebuilt serialize-javascript to address 2 CVEs. Fixed in 6.0.2-tuxcare.3.","status":"published","published":"2026-10-27T11:07:07Z","modified":"2026-10-27T13:30:09.264662686Z","updated_at":"2026-11-02T15:43:55.34846Z"},{"id":"CLSA-2026-1793125688","title":"TuxCare security update for serialize-javascript (2 CVEs)","description":"TuxCare rebuilt serialize-javascript to address 2 CVEs. Fixed in 7.1.1-tuxcare.2.","status":"published","published":"2026-10-27T18:28:08Z","modified":"2026-10-27T19:30:07.245816471Z","updated_at":"2026-11-02T15:43:55.34846Z"},{"id":"CLSA-2026-1793180818","title":"TuxCare security update for serialize-javascript (1 CVE)","description":"TuxCare rebuilt serialize-javascript to address 1 CVE. Fixed in 6.0.1-tuxcare.1.","status":"published","published":"2026-10-28T09:46:58Z","modified":"2026-10-28T13:45:17.236315133Z","updated_at":"2026-11-02T15:43:55.34846Z"},{"id":"CLSA-2026-1793183866","title":"TuxCare security update for serialize-javascript (1 CVE)","description":"TuxCare rebuilt serialize-javascript to address 1 CVE. Fixed in 6.0.0-tuxcare.1.","status":"published","published":"2026-10-28T10:37:46Z","modified":"2026-10-28T13:45:02.682825262Z","updated_at":"2026-11-02T15:43:55.34846Z"},{"id":"CLSA-2026-1793187934","title":"TuxCare security update for serialize-javascript (1 CVE)","description":"TuxCare rebuilt serialize-javascript to address 1 CVE. Fixed in 5.0.1-tuxcare.3.","status":"published","published":"2026-10-28T11:45:34Z","modified":"2026-10-28T13:45:14.328532008Z","updated_at":"2026-11-02T15:43:55.34846Z"},{"id":"CLSA-2026-1793207115","title":"TuxCare security update for serialize-javascript (1 CVE)","description":"TuxCare rebuilt serialize-javascript to address 1 CVE. Fixed in 3.1.0-tuxcare.2.","status":"published","published":"2026-10-28T17:05:15Z","modified":"2026-10-28T19:45:12.961051918Z","updated_at":"2026-11-02T15:43:55.669514Z"},{"id":"CLSA-2026-1793209309","title":"TuxCare security update for serialize-javascript (1 CVE)","description":"TuxCare rebuilt serialize-javascript to address 1 CVE. Fixed in 2.1.2-tuxcare.2.","status":"published","published":"2026-10-28T17:41:49Z","modified":"2026-10-28T19:45:12.039932101Z","updated_at":"2026-11-02T15:43:55.669514Z"},{"id":"CLSA-2026-1793789998","title":"TuxCare security update for serialize-javascript (3 CVEs)","description":"TuxCare rebuilt serialize-javascript to address 3 CVEs. Fixed in 3.0.0-tuxcare.1.","status":"published","published":"2026-11-04T11:59:59Z","modified":"2026-11-04T14:45:06.68236267Z","updated_at":"2026-11-04T15:03:54.132276Z"},{"id":"CLSA-2026-1793790235","title":"TuxCare security update for serialize-javascript (2 CVEs)","description":"TuxCare rebuilt serialize-javascript to address 2 CVEs. Fixed in 7.0.7-tuxcare.1.","status":"published","published":"2026-11-04T12:03:56Z","modified":"2026-11-07T19:00:37.503451187Z","updated_at":"2026-11-07T19:21:34.633914Z"},{"id":"openSUSE-SU-2026:12424-1","title":"agama-web-ui-25+475.275dd4727-56.1 on GA media","description":"These are all security issues fixed in the agama-web-ui-25+475.275dd4727-56.1 package on the GA media of openSUSE Tumbleweed.","status":"published","published":"2026-11-05T00:00:00Z","modified":"2026-11-06T17:23:11.345171291Z","updated_at":"2026-11-06T18:05:03.243497Z"}]}}