{"id":2168341,"date":"2026-11-18T11:12:59","date_gmt":"2026-11-18T10:12:59","guid":{"rendered":"https:\/\/kohenavocats.fr\/?p=2168341"},"modified":"2026-11-18T11:12:59","modified_gmt":"2026-11-18T10:12:59","slug":"java-vulnerability-uk-business-patch-report-liability","status":"publish","type":"post","link":"https:\/\/kohenavocats.fr\/en\/2026\/11\/18\/java-vulnerability-uk-business-patch-report-liability\/","title":{"rendered":"Java Vulnerability: Who Must Patch, Report and Pay When a UK Business Is Exposed?"},"content":{"rendered":"<p>Java vulnerability is a rising search query in the United Kingdom this week. Behind the technical question sits a legal one for every business that runs Java-based software, directly or through a supplier: who has to act, what has to be reported, and who bears the cost if systems are exposed. This article does not describe or assess any particular flaw. It sets out the rules of the United Kingdom that apply once a vulnerability in software a business relies on becomes public, as read on the official legislation database on 18 November 2026. Four sets of rules do most of the work: the Network and Information Systems Regulations 2018 for regulated operators and larger digital service providers; the implied term of care and skill and the controls on exclusion clauses that govern contracts with IT suppliers in England and Wales and Northern Ireland; the duty of care that company directors owe to their company; and the Computer Misuse Act 1990, which limits how far a business may go when it tests systems for exposure. A short passage covers manufacturers of connectable products. The discussion is general in scope: it describes checks useful in comparable situations and makes no finding about any software publisher, supplier or user. Scots contract law follows its own rules and is not covered, and data protection law, which forms a separate regime, is outside this article.<\/p>\n<p>By Reda Kohen, a lawyer admitted to the Paris Bar. This article provides general information on foreign law.<\/p>\n<h2>I. Who Has to Act When a Vulnerability Is Disclosed in Software a UK Business Uses?<\/h2>\n<p>The rules examined here do not impose a single patching deadline on every business. Who must do what depends first on the position of the business. A defined group of operators and digital service providers carries a statutory security duty enforced by a regulator. Other businesses find their obligations in their contracts and, where they are companies, in the general duties of their directors. Identifying which group a business belongs to is the first step, because it decides whether a regulator can ask questions about the response.<\/p>\n<h3>A. Operators of essential services and digital service providers carry a statutory security duty<\/h3>\n<p>The <a href=\"https:\/\/www.legislation.gov.uk\/uksi\/2018\/506\">Network and Information Systems Regulations 2018<\/a> apply across the United Kingdom. Under regulation 8(1), a person who provides an essential service of a kind listed in Schedule 2 is deemed to be designated as an operator of an essential service, or OES, where that service relies on network and information systems and satisfies the threshold set for that kind of service. Schedule 2 and its thresholds cover subsectors such as electricity, oil, gas, air, water and rail transport, road authorities, healthcare settings and digital infrastructure, among others. A competent authority may also designate a provider that falls below the threshold, under regulation 8(3), where it concludes that an incident affecting the service is likely to have significant disruptive effects on its provision. A person who meets the criteria in regulation 8(1) must notify the designated competent authority in writing, under regulation 8(2).<\/p>\n<p>The same Regulations reach a second group, relevant digital service providers, or RDSPs. Regulation 1(3)(e) applies that label to a person who provides a digital service in the United Kingdom, whose head office is in the United Kingdom or who has nominated a representative established there, and who is not a micro or small enterprise. Regulation 12(1) names the three services concerned: online marketplaces, online search engines and cloud computing services. Regulation 1 describes a cloud computing service as a digital service that enables access to a scalable and elastic pool of shareable computing resources. A business that offers Java-based applications to customers as a hosted platform should therefore check whether its offer meets that definition and whether it exceeds the size condition, because the answer decides whether the regime applies to it at all.<\/p>\n<p>For an OES, <a href=\"https:\/\/www.legislation.gov.uk\/uksi\/2018\/506\">regulation 10<\/a> requires \u201cappropriate and proportionate technical and organisational measures to manage risks posed to the security of the network and information systems on which their essential service relies\u201d. Regulation 10(2) adds a duty to take appropriate and proportionate measures to prevent and minimise the impact of incidents, with a view to ensuring the continuity of the service. Regulation 10(3) requires the measures to ensure a level of security appropriate to the risk posed, having regard to the state of the art. Regulation 10(4) requires operators to have regard to any relevant guidance issued by their competent authority. Each sector therefore reads the general duty alongside the guidance of its own authority.<\/p>\n<p>For an RDSP, regulation 12(1) and (2) impose a parallel duty to identify and take appropriate and proportionate measures to manage the risks to the systems on which it relies to provide its services. The measures must ensure a level of security appropriate to the risk, having regard to the state of the art, and must prevent and minimise the impact of incidents with a view to continuity. Regulation 12(2)(c) lists the elements they must take into account: the security of systems and facilities, incident handling, business continuity management, monitoring, auditing and testing, and compliance with international standards.<\/p>\n<p>None of these provisions fixes a number of days within which a security update must be installed. They frame the question as one of risk management. When a vulnerability is disclosed in a component used by an essential or digital service, the practical test under regulations 10 and 12 is whether the operator identified the exposure, assessed it against the service it supports, and took measures proportionate to that risk. Those measures can include applying a vendor update, applying a documented mitigation while an update is tested, isolating an exposed system, or accepting a residual risk for reasons recorded at the time. The operator&#8217;s records are the only reliable way to show, afterwards, what it knew and what it decided at each stage. A short entry per system, giving the date the exposure was confirmed, the measure chosen and the person who approved it, usually tells that story better than a long report written weeks later.<\/p>\n<p>The enforcement route is set out in regulations 17 and 18. Under regulation 17(1), the designated competent authority may serve an enforcement notice on an OES if it has reasonable grounds to believe that the operator failed to fulfil the security duties under regulation 10(1) and (2), or failed to notify a NIS incident or to comply with the notification requirements. Regulation 18 allows a notice of intention to impose a penalty, followed, after any representations, by a penalty notice. Under regulation 18(6), a penalty may not exceed \u00a31,000,000 for a contravention that is not material, \u00a38,500,000 for a material contravention outside the most serious category, and \u00a317,000,000 for a material contravention which has or could have created a significant risk to, or significant impact on, the service provision. Regulation 19A gives an OES or an RDSP a right of appeal, on the grounds it specifies, against the measures it lists, which include the service of enforcement notices and penalty notices. Since 30 September 2026, the consolidated text names the Information Commission as the authority that receives RDSP incident notifications and may serve penalty notices on RDSPs, following consequential amendments made in 2026 in connection with the Data (Use and Access) Act 2025. The official consolidated text is stated to be up to date with changes in force on or before 16 November 2026, and it flags changes that may be brought into force at a future date, so the current version should be checked before relying on any provision.<\/p>\n<h3>B. Other businesses: the contract with the IT supplier and the board&#8217;s duty of care<\/h3>\n<p>Most businesses running Java-based software are neither operators of essential services nor relevant digital service providers. For them, the rules examined here do not create a regulatory duty to patch within a set time. Their position depends on who agreed to do what and, for companies, on how the board exercises its general duty of care. That is less a gap than a shift: the questions move from a regulator&#8217;s file to a contract file and a board file.<\/p>\n<p>Where a business has outsourced the management of its systems, the starting point in England and Wales and Northern Ireland is the <a href=\"https:\/\/www.legislation.gov.uk\/ukpga\/1982\/29\/section\/13\">Supply of Goods and Services Act 1982, section 13<\/a>. In a relevant contract for the supply of a service where the supplier is acting in the course of a business, \u201cthere is an implied term that the supplier will carry out the service with reasonable care and skill\u201d. The term is implied by statute, so it applies even where the written contract is silent on the standard of performance.<\/p>\n<p><a href=\"https:\/\/www.legislation.gov.uk\/ukpga\/1982\/29\/section\/12\">Section 12<\/a> defines that relevant contract as one under which a person agrees to carry out a service, other than a contract to which Chapter 4 of Part 1 of the Consumer Rights Act 2015 applies, so the 1982 Act governs the business-to-business services discussed here. Section 12(3) adds that the contract qualifies whether or not goods are also transferred or hired under it, which covers a managed service that bundles hardware, licences and support.<\/p>\n<p>The implied term attaches to the service the supplier agreed to carry out. It does not create a service the parties never agreed. The first document to read is therefore the scope: whether the supplier undertook to monitor security advisories, to apply updates, to manage the runtime environments on which Java-based applications operate, or only to host servers that the customer administers itself. A managed service agreement that lists patch management among the services, with response times by severity, gives a measurable standard. A hosting agreement under which the customer keeps administrative control is likely to leave the update decision with the customer. Between the two, change logs, tickets and the supplier&#8217;s own notices show how the parties actually divided the work, which helps when the written scope is vague or out of date.<\/p>\n<p>Where patching falls within the agreed service, the term looks at how the service was carried out rather than at the outcome alone. A supplier that tracked the advisory, assessed which customer systems used the affected component, scheduled or applied the update, and told the customer about any residual exposure is in a different position from one that took no step after the advisory was published. The customer&#8217;s own conduct also counts. If it refused a maintenance window, delayed approval of a change or kept an unsupported version in service against advice, the record of that choice matters to any later claim. The same reasoning applies to a software vendor&#8217;s support and maintenance services where they are supplied under a contract governed by the law of England and Wales or Northern Ireland, subject to the controls on exclusion clauses discussed in part II.<\/p>\n<p>For a company, the board&#8217;s role is governed by the <a href=\"https:\/\/www.legislation.gov.uk\/ukpga\/2006\/46\/section\/174\">Companies Act 2006, section 174<\/a>: \u201cA director of a company must exercise reasonable care, skill and diligence.\u201d Section 174(2) measures that care against a reasonably diligent person with the general knowledge, skill and experience that may reasonably be expected of a person carrying out the functions carried out by the director in relation to the company, and with the general knowledge, skill and experience that the director actually has. Under <a href=\"https:\/\/www.legislation.gov.uk\/ukpga\/2006\/46\/section\/170\">section 170(1)<\/a>, the general duties in sections 171 to 177 are owed by a director to the company, which means that the duty concerns the director&#8217;s relationship with the company rather than with its customers or suppliers.<\/p>\n<p>Section 174 does not mention cyber security, and it does not require directors to manage software updates themselves. What it can make relevant is the way the board responds once it has been told that a serious flaw affects systems on which the business depends. A board that asks which systems are exposed, who is responsible for the fix, what it will cost and when it will be done, and that records the answers, exercises its oversight in a way that can later be shown. A director with technical expertise is measured against that expertise as well, under the second limb of section 174(2). The practical output is a short board note: exposure, owner, decision, date and residual risk. For a smaller company without a board committee, an email from the director to the IT supplier asking the same questions, with the replies kept on file, serves the same purpose.<\/p>\n<h2>II. What Must Be Reported, Tested and Recorded Once the Flaw Is Known?<\/h2>\n<p>Once a business knows that it may be exposed, three practical questions follow. Does anything have to be reported, and when? How can exposure be tested without breaking the law? And what evidence will matter if the episode ends in a dispute with a supplier? The answers come from different instruments, which is why they are best handled as separate tasks with separate owners.<\/p>\n<h3>A. A disclosed vulnerability is not, by itself, a notifiable incident under the NIS Regulations<\/h3>\n<p>The notification duties in the <a href=\"https:\/\/www.legislation.gov.uk\/uksi\/2018\/506\">Network and Information Systems Regulations 2018<\/a> are triggered by incidents, and regulation 1 defines an incident as \u201cany event having an actual adverse effect on the security of network and information systems\u201d. The security of those systems is defined as their ability to resist, at a given level of confidence, any action that compromises the availability, authenticity, integrity or confidentiality of stored, transmitted or processed data or of the related services. On that definition, a published vulnerability that has not been exploited and has not affected any system is a risk to be managed under regulation 10 or 12. It becomes relevant to the notification rules once an event has an actual adverse effect on security.<\/p>\n<p>For an OES, regulation 11(1) requires notification of any incident which has a significant impact on the continuity of the essential service, which the Regulations call a NIS incident. Regulation 11(2) lists the factors for judging significance: the number of users affected by the disruption, the duration of the incident and the geographical area affected. The notice must give the operator&#8217;s name and services, the time and duration of the incident, its nature and impact, any likely cross-border impact and any other helpful information. Under <a href=\"https:\/\/www.legislation.gov.uk\/uksi\/2018\/506\">regulation 11(3)<\/a>, it must be provided \u201cwithout undue delay and in any event no later than 72 hours after the operator is aware that a NIS incident has occurred\u201d, in the form and manner the competent authority determines. Under regulation 11(4), the information required is limited to what may reasonably be expected to be within the operator&#8217;s knowledge, which matters when an investigation is still under way at the time of the notice.<\/p>\n<p>For an RDSP, regulation 12(3) requires notification of any incident having a substantial impact on the provision of its online marketplace, search engine or cloud computing service. Regulation 12(4) applies that requirement only if the provider has access to information enabling it to assess whether the impact is substantial. Under regulation 12(6), the notification must be made without undue delay and no later than 72 hours after the provider is first aware that an incident has occurred, and it must contain enough information for the Information Commission to determine the significance of any cross-border impact. Regulation 12(7) lists the parameters for assessing whether the impact is substantial, including the number of users affected, in particular users relying on the service to provide their own services, the duration, the geographical area, the extent of the disruption and the impact on economic and societal activities.<\/p>\n<p>Regulation 12(9) links the two regimes. If an OES relies on an RDSP to provide an essential service, the operator must notify its designated competent authority in writing, without undue delay, of any significant impact on the continuity of the service it provides caused by an incident affecting that provider. An operator running Java-based workloads on a third-party cloud platform therefore needs a contractual channel through which the provider tells it promptly about incidents, because its own duty to report depends on that information reaching it.<\/p>\n<p>Notification is not the end of the matter. After receiving a notice, the competent authority must assess what further action is required, under regulation 11(5), and the authority or the national computer security incident response team may inform the public under regulation 11(7)(b) if it considers public awareness necessary to handle the incident or prevent a future one. Regulation 11(8) requires them to consult the operator before doing so. A business should therefore prepare its customer communication alongside the notice, so that it is not caught out by a public statement it has not anticipated.<\/p>\n<p>In practice, the file should separate three moments: when the vulnerability became known to the business, when the business established whether it used the affected component, and when, if ever, it found evidence of an actual adverse effect. Under the wording of regulations 11(3) and 12(6), the 72-hour period runs from awareness that an incident, or for an OES a NIS incident, has occurred. It is therefore the third moment that matters for timing, provided the impact reaches the threshold set by regulation 11 or 12. Recording these steps as they happen avoids reconstructing them later from memory. Where personal data may be affected, data protection law forms a separate regime that has to be checked in parallel.<\/p>\n<h3>B. Test lawfully, enforce the contract and keep the evidence<\/h3>\n<p>Businesses often want to know quickly whether they are exposed, and some staff will look for tools that test for the flaw. The <a href=\"https:\/\/www.legislation.gov.uk\/ukpga\/1990\/18\/section\/1\">Computer Misuse Act 1990, section 1<\/a> makes it an offence for a person to cause a computer to perform any function with intent to secure access to any program or data held in any computer, where the access intended is unauthorised and the person knows at that time that it is. Section 1(2) provides that the intent need not be directed at any particular program or data, at a program or data of any particular kind, or at a program or data held in any particular computer. On conviction on indictment, section 1(3) sets a maximum of two years&#8217; imprisonment, a fine or both. Testing a system that the business owns or is authorised to test is a different situation from probing a third party&#8217;s server to see whether it is vulnerable, which could meet the elements of section 1 if access is intended and not authorised.<\/p>\n<p>Exploit code raises a second question. Under <a href=\"https:\/\/www.legislation.gov.uk\/ukpga\/1990\/18\/section\/3A\">section 3A<\/a>, a person commits an offence if they make, adapt, supply or offer to supply any article intending it to be used to commit, or to assist in the commission of, an offence under section 1, 3 or 3ZA. Section 3A(2) covers supplying or offering to supply an article believing that it is likely to be so used, and section 3A(3) covers obtaining an article with such an intention or with a view to its being supplied for that use. Section 3A(4) states that an article includes any program or data held in electronic form. A business that circulates proof-of-concept code should therefore limit it to people who need it for authorised testing, record the purpose and the authorised scope, and avoid posting it where it is likely to be used against other people&#8217;s systems.<\/p>\n<p>A short written authorisation before any test answers most of these questions. It should name the systems in scope, the owner who authorises the work, the method, the time window and the person responsible. For systems hosted by a supplier, the supplier&#8217;s consent, or the contract clause that permits security testing, should be on file, because the business may not be the party entitled to authorise access to the supplier&#8217;s infrastructure. The same document helps later: it shows that the business acted to understand its exposure and stayed within agreed limits while doing so.<\/p>\n<p>When the exposure causes loss and the business looks to its supplier, the contract will often contain a cap or an exclusion. In England and Wales and Northern Ireland, <a href=\"https:\/\/www.legislation.gov.uk\/ukpga\/1977\/50\/section\/3\">section 3 of the Unfair Contract Terms Act 1977<\/a> applies where one party deals on the other&#8217;s written standard terms of business. Against that party, the other cannot, when itself in breach, exclude or restrict its liability for the breach, or claim to be entitled to render a contractual performance substantially different from what was reasonably expected of it or no performance at all, except in so far as the term satisfies the requirement of reasonableness. Under <a href=\"https:\/\/www.legislation.gov.uk\/ukpga\/1977\/50\/section\/2\">section 2(2)<\/a>, liability for negligence causing loss or damage other than death or personal injury can be excluded or restricted only in so far as the term or notice satisfies that same requirement. Both sections state that they do not apply to consumer contracts, which are dealt with under the Consumer Rights Act 2015.<\/p>\n<p><a href=\"https:\/\/www.legislation.gov.uk\/ukpga\/1977\/50\/section\/11\">Section 11<\/a> explains how reasonableness is judged. Under section 11(1), the term must have been a fair and reasonable one to include \u201chaving regard to the circumstances which were, or ought reasonably to have been, known to or in the contemplation of the parties when the contract was made\u201d. Where a term limits liability to a specified sum, section 11(4) directs attention to the resources the supplier could expect to have available to meet the liability and to how far it was open to the supplier to cover itself by insurance. Section 11(5) puts the burden on the party claiming that the term satisfies the requirement of reasonableness. For a customer, the useful file therefore contains the signed contract and the standard terms actually incorporated, the negotiation correspondence, the service levels, any statements the supplier made about its insurance, and the timeline of the supplier&#8217;s response to the advisory. For a supplier, the same file shows why the cap was proportionate when the contract was signed.<\/p>\n<p>Manufacturers of the connectable products covered by the <a href=\"https:\/\/www.legislation.gov.uk\/uksi\/2023\/1007\">Product Security and Telecommunications Infrastructure (Security Requirements for Relevant Connectable Products) Regulations 2023<\/a> face a specific disclosure regime. These Regulations came into force on 29 April 2024 and extend to England and Wales, Scotland and Northern Ireland. Schedule 1, paragraph 2, requires the publication of at least one point of contact through which a person can report security issues relating to the product&#8217;s hardware and software, together with information on when that person will receive an acknowledgment of receipt and status updates until the reported issues are resolved. Paragraph 3 requires the defined support period, meaning the minimum length of time for which security updates will be provided, to be published, and states that the requirement is not met if that period is shortened after publication. Schedule 3, paragraph 5, excepts desktop and laptop computers and tablets without cellular connectivity, unless they are designed exclusively for children under 14. For a manufacturer whose connected product embeds an affected component, the published contact point is the channel through which reports about it are expected to arrive, and the published support period tells customers for how long security updates are to be provided.<\/p>\n<p>Groups that also operate in France face the French side of the same episode under French law, which is the subject of the firm&#8217;s <a href=\"https:\/\/kohenavocats.fr\/en\/business-law-attorneys-paris-75017\/\">business law practice in Paris<\/a>. The United Kingdom duties described here follow their own rules and timetable. A single incident log, kept by system and by country, lets each set of advisers work from the same facts without mixing the obligations of two legal systems.<\/p>\n<h2>Conclusion<\/h2>\n<p>A vulnerability in widely used software turns into a legal question in three steps. First, identify the position of the business. An operator of an essential service or a relevant digital service provider carries a statutory security duty, a 72-hour reporting rule for qualifying incidents and exposure to regulatory penalties. Other businesses find their obligations in their contracts and, for companies, in the directors&#8217; duty of care owed to the company.<\/p>\n<p>Second, keep the vulnerability and the incident apart. A disclosed flaw calls for risk management and documented decisions. A notification duty under the NIS Regulations arises only once an event has an actual adverse effect and, for regulated operators and providers, reaches the significance threshold. Third, stay within the law while testing and preserve the contract record. Authorised testing, controlled handling of exploit code, a clear reading of the supplier&#8217;s scope and of any liability cap, and a dated log of each decision leave the business able to show what it knew, what it decided and why.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>When a Java vulnerability reaches a UK business, the law splits the work: NIS security and 72-hour incident duties, supplier contracts, directors&#8217; care and lawful testing.<\/p>\n","protected":false},"author":251031309,"featured_media":16445,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_kj_source_type":"","_kj_official_id":"","_kj_official_url":"","_kj_judilibre_id":"","_kj_jur":"","_kj_lieu":"","_kj_chambre":"","_kj_rg":"","_kj_date":"","activitypub_content_warning":"","activitypub_content_visibility":"","activitypub_max_image_attachments":4,"activitypub_interaction_policy_quote":"anyone","activitypub_status":"federated","footnotes":""},"categories":[80335,80333],"tags":[],"class_list":["post-2168341","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-us-uk-business-law","category-us-uk-law"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v28.2 (Yoast SEO v28.2) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Java Vulnerability: Who Must Patch, Report and Pay When a UK Business Is Exposed?<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/kohenavocats.fr\/en\/2026\/11\/18\/java-vulnerability-uk-business-patch-report-liability\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Java Vulnerability: Who Must Patch, Report and Pay When a UK Business Is Exposed?\" \/>\n<meta property=\"og:description\" content=\"When a Java vulnerability reaches a UK business, the law splits the work: NIS security and 72-hour incident duties, supplier contracts, directors&#039; care and lawful testing.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/kohenavocats.fr\/en\/2026\/11\/18\/java-vulnerability-uk-business-patch-report-liability\/\" \/>\n<meta property=\"og:site_name\" content=\"Reda KOHEN\" \/>\n<meta property=\"article:published_time\" content=\"2026-11-18T10:12:59+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/kohenavocats.fr\/wp-content\/uploads\/2024\/11\/steve-johnson-GMZq7FZRcvc-unsplash-scaled.webp\" \/>\n\t<meta property=\"og:image:width\" content=\"6720\" \/>\n\t<meta property=\"og:image:height\" content=\"3780\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/webp\" \/>\n<meta name=\"author\" content=\"Kohen\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Kohen\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"20 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/2026\\\/11\\\/18\\\/java-vulnerability-uk-business-patch-report-liability\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/2026\\\/11\\\/18\\\/java-vulnerability-uk-business-patch-report-liability\\\/\"},\"author\":{\"name\":\"Kohen\",\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/#\\\/schema\\\/person\\\/6254a643e6239d803134a01c800381bd\"},\"headline\":\"Java Vulnerability: Who Must Patch, Report and Pay When a UK Business Is Exposed?\",\"datePublished\":\"2026-11-18T10:12:59+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/2026\\\/11\\\/18\\\/java-vulnerability-uk-business-patch-report-liability\\\/\"},\"wordCount\":3995,\"publisher\":{\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/2026\\\/11\\\/18\\\/java-vulnerability-uk-business-patch-report-liability\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/kohenavocats.fr\\\/wp-content\\\/uploads\\\/2024\\\/11\\\/steve-johnson-GMZq7FZRcvc-unsplash-scaled.webp\",\"articleSection\":[\"US &amp; UK Business Law\",\"US &amp; UK Law\"],\"inLanguage\":\"en-US\",\"citation\":\"Java Vulnerability: Who Must Patch, Report and Pay When a UK Business Is Exposed?\",\"about\":[{\"@type\":\"Thing\",\"name\":\"US &amp; UK Business Law\"},{\"@type\":\"Thing\",\"name\":\"US &amp; UK Law\"}],\"dateModified\":\"2026-11-18T10:12:59+00:00\",\"speakable\":{\"@type\":\"SpeakableSpecification\",\"cssSelector\":[\".article-content > p:first-of-type\"]}},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/2026\\\/11\\\/18\\\/java-vulnerability-uk-business-patch-report-liability\\\/\",\"url\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/2026\\\/11\\\/18\\\/java-vulnerability-uk-business-patch-report-liability\\\/\",\"name\":\"Java Vulnerability: Who Must Patch, Report and Pay When a UK Business Is Exposed?\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/2026\\\/11\\\/18\\\/java-vulnerability-uk-business-patch-report-liability\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/2026\\\/11\\\/18\\\/java-vulnerability-uk-business-patch-report-liability\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/kohenavocats.fr\\\/wp-content\\\/uploads\\\/2024\\\/11\\\/steve-johnson-GMZq7FZRcvc-unsplash-scaled.webp\",\"datePublished\":\"2026-11-18T10:12:59+00:00\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/2026\\\/11\\\/18\\\/java-vulnerability-uk-business-patch-report-liability\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/2026\\\/11\\\/18\\\/java-vulnerability-uk-business-patch-report-liability\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/2026\\\/11\\\/18\\\/java-vulnerability-uk-business-patch-report-liability\\\/#primaryimage\",\"url\":\"https:\\\/\\\/kohenavocats.fr\\\/wp-content\\\/uploads\\\/2024\\\/11\\\/steve-johnson-GMZq7FZRcvc-unsplash-scaled.webp\",\"contentUrl\":\"https:\\\/\\\/kohenavocats.fr\\\/wp-content\\\/uploads\\\/2024\\\/11\\\/steve-johnson-GMZq7FZRcvc-unsplash-scaled.webp\",\"width\":6720,\"height\":3780},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/2026\\\/11\\\/18\\\/java-vulnerability-uk-business-patch-report-liability\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Java Vulnerability: Who Must Patch, Report and Pay When a UK Business Is Exposed?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/#website\",\"url\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/\",\"name\":\"Reda KOHEN\",\"description\":\"Ma\u00eetre Reda Kohen, attorney specialized in real estate and business law in Paris, advises and assists companies and individuals in their real estate, commercial and contractual transactions. He also handles real estate litigation and the resolution of complex commercial disputes.\",\"publisher\":{\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/#organization\",\"name\":\"Reda KOHEN\",\"url\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/kohenavocats.fr\\\/wp-content\\\/uploads\\\/2024\\\/05\\\/Logo-2-1.webp\",\"contentUrl\":\"https:\\\/\\\/kohenavocats.fr\\\/wp-content\\\/uploads\\\/2024\\\/05\\\/Logo-2-1.webp\",\"width\":2114,\"height\":1253,\"caption\":\"Reda KOHEN\"},\"image\":{\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/#\\\/schema\\\/logo\\\/image\\\/\"}},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/#\\\/schema\\\/person\\\/6254a643e6239d803134a01c800381bd\",\"name\":\"Kohen\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/1c5e76ef76bbbfdd2b4da984e2bf2fa4056fd51a27d25ce2c332047f1dfd6e00?s=96&d=identicon&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/1c5e76ef76bbbfdd2b4da984e2bf2fa4056fd51a27d25ce2c332047f1dfd6e00?s=96&d=identicon&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/1c5e76ef76bbbfdd2b4da984e2bf2fa4056fd51a27d25ce2c332047f1dfd6e00?s=96&d=identicon&r=g\",\"caption\":\"Kohen\"},\"url\":\"https:\\\/\\\/kohenavocats.fr\\\/en\\\/author\\\/kohenmlk\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Java Vulnerability: Who Must Patch, Report and Pay When a UK Business Is Exposed?","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/kohenavocats.fr\/en\/2026\/11\/18\/java-vulnerability-uk-business-patch-report-liability\/","og_locale":"en_US","og_type":"article","og_title":"Java Vulnerability: Who Must Patch, Report and Pay When a UK Business Is Exposed?","og_description":"When a Java vulnerability reaches a UK business, the law splits the work: NIS security and 72-hour incident duties, supplier contracts, directors' care and lawful testing.","og_url":"https:\/\/kohenavocats.fr\/en\/2026\/11\/18\/java-vulnerability-uk-business-patch-report-liability\/","og_site_name":"Reda KOHEN","article_published_time":"2026-11-18T10:12:59+00:00","og_image":[{"width":6720,"height":3780,"url":"https:\/\/kohenavocats.fr\/wp-content\/uploads\/2024\/11\/steve-johnson-GMZq7FZRcvc-unsplash-scaled.webp","type":"image\/webp"}],"author":"Kohen","twitter_card":"summary_large_image","twitter_misc":{"Written by":"Kohen","Est. reading time":"20 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/kohenavocats.fr\/en\/2026\/11\/18\/java-vulnerability-uk-business-patch-report-liability\/#article","isPartOf":{"@id":"https:\/\/kohenavocats.fr\/en\/2026\/11\/18\/java-vulnerability-uk-business-patch-report-liability\/"},"author":{"name":"Kohen","@id":"https:\/\/kohenavocats.fr\/en\/#\/schema\/person\/6254a643e6239d803134a01c800381bd"},"headline":"Java Vulnerability: Who Must Patch, Report and Pay When a UK Business Is Exposed?","datePublished":"2026-11-18T10:12:59+00:00","mainEntityOfPage":{"@id":"https:\/\/kohenavocats.fr\/en\/2026\/11\/18\/java-vulnerability-uk-business-patch-report-liability\/"},"wordCount":3995,"publisher":{"@id":"https:\/\/kohenavocats.fr\/en\/#organization"},"image":{"@id":"https:\/\/kohenavocats.fr\/en\/2026\/11\/18\/java-vulnerability-uk-business-patch-report-liability\/#primaryimage"},"thumbnailUrl":"https:\/\/kohenavocats.fr\/wp-content\/uploads\/2024\/11\/steve-johnson-GMZq7FZRcvc-unsplash-scaled.webp","articleSection":["US &amp; UK Business Law","US &amp; UK Law"],"inLanguage":"en-US","citation":"Java Vulnerability: Who Must Patch, Report and Pay When a UK Business Is Exposed?","about":[{"@type":"Thing","name":"US &amp; UK Business Law"},{"@type":"Thing","name":"US &amp; UK Law"}],"dateModified":"2026-11-18T10:12:59+00:00","speakable":{"@type":"SpeakableSpecification","cssSelector":[".article-content > p:first-of-type"]}},{"@type":"WebPage","@id":"https:\/\/kohenavocats.fr\/en\/2026\/11\/18\/java-vulnerability-uk-business-patch-report-liability\/","url":"https:\/\/kohenavocats.fr\/en\/2026\/11\/18\/java-vulnerability-uk-business-patch-report-liability\/","name":"Java Vulnerability: Who Must Patch, Report and Pay When a UK Business Is Exposed?","isPartOf":{"@id":"https:\/\/kohenavocats.fr\/en\/#website"},"primaryImageOfPage":{"@id":"https:\/\/kohenavocats.fr\/en\/2026\/11\/18\/java-vulnerability-uk-business-patch-report-liability\/#primaryimage"},"image":{"@id":"https:\/\/kohenavocats.fr\/en\/2026\/11\/18\/java-vulnerability-uk-business-patch-report-liability\/#primaryimage"},"thumbnailUrl":"https:\/\/kohenavocats.fr\/wp-content\/uploads\/2024\/11\/steve-johnson-GMZq7FZRcvc-unsplash-scaled.webp","datePublished":"2026-11-18T10:12:59+00:00","breadcrumb":{"@id":"https:\/\/kohenavocats.fr\/en\/2026\/11\/18\/java-vulnerability-uk-business-patch-report-liability\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/kohenavocats.fr\/en\/2026\/11\/18\/java-vulnerability-uk-business-patch-report-liability\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/kohenavocats.fr\/en\/2026\/11\/18\/java-vulnerability-uk-business-patch-report-liability\/#primaryimage","url":"https:\/\/kohenavocats.fr\/wp-content\/uploads\/2024\/11\/steve-johnson-GMZq7FZRcvc-unsplash-scaled.webp","contentUrl":"https:\/\/kohenavocats.fr\/wp-content\/uploads\/2024\/11\/steve-johnson-GMZq7FZRcvc-unsplash-scaled.webp","width":6720,"height":3780},{"@type":"BreadcrumbList","@id":"https:\/\/kohenavocats.fr\/en\/2026\/11\/18\/java-vulnerability-uk-business-patch-report-liability\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/kohenavocats.fr\/en\/"},{"@type":"ListItem","position":2,"name":"Java Vulnerability: Who Must Patch, Report and Pay When a UK Business Is Exposed?"}]},{"@type":"WebSite","@id":"https:\/\/kohenavocats.fr\/en\/#website","url":"https:\/\/kohenavocats.fr\/en\/","name":"Reda KOHEN","description":"Ma\u00eetre Reda Kohen, attorney specialized in real estate and business law in Paris, advises and assists companies and individuals in their real estate, commercial and contractual transactions. He also handles real estate litigation and the resolution of complex commercial disputes.","publisher":{"@id":"https:\/\/kohenavocats.fr\/en\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/kohenavocats.fr\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/kohenavocats.fr\/en\/#organization","name":"Reda KOHEN","url":"https:\/\/kohenavocats.fr\/en\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/kohenavocats.fr\/en\/#\/schema\/logo\/image\/","url":"https:\/\/kohenavocats.fr\/wp-content\/uploads\/2024\/05\/Logo-2-1.webp","contentUrl":"https:\/\/kohenavocats.fr\/wp-content\/uploads\/2024\/05\/Logo-2-1.webp","width":2114,"height":1253,"caption":"Reda KOHEN"},"image":{"@id":"https:\/\/kohenavocats.fr\/en\/#\/schema\/logo\/image\/"}},{"@type":"Person","@id":"https:\/\/kohenavocats.fr\/en\/#\/schema\/person\/6254a643e6239d803134a01c800381bd","name":"Kohen","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/secure.gravatar.com\/avatar\/1c5e76ef76bbbfdd2b4da984e2bf2fa4056fd51a27d25ce2c332047f1dfd6e00?s=96&d=identicon&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/1c5e76ef76bbbfdd2b4da984e2bf2fa4056fd51a27d25ce2c332047f1dfd6e00?s=96&d=identicon&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/1c5e76ef76bbbfdd2b4da984e2bf2fa4056fd51a27d25ce2c332047f1dfd6e00?s=96&d=identicon&r=g","caption":"Kohen"},"url":"https:\/\/kohenavocats.fr\/en\/author\/kohenmlk\/"}]}},"_links":{"self":[{"href":"https:\/\/kohenavocats.fr\/en\/wp-json\/wp\/v2\/posts\/2168341","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/kohenavocats.fr\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/kohenavocats.fr\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/kohenavocats.fr\/en\/wp-json\/wp\/v2\/users\/251031309"}],"replies":[{"embeddable":true,"href":"https:\/\/kohenavocats.fr\/en\/wp-json\/wp\/v2\/comments?post=2168341"}],"version-history":[{"count":1,"href":"https:\/\/kohenavocats.fr\/en\/wp-json\/wp\/v2\/posts\/2168341\/revisions"}],"predecessor-version":[{"id":2168342,"href":"https:\/\/kohenavocats.fr\/en\/wp-json\/wp\/v2\/posts\/2168341\/revisions\/2168342"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/kohenavocats.fr\/en\/wp-json\/wp\/v2\/media\/16445"}],"wp:attachment":[{"href":"https:\/\/kohenavocats.fr\/en\/wp-json\/wp\/v2\/media?parent=2168341"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/kohenavocats.fr\/en\/wp-json\/wp\/v2\/categories?post=2168341"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/kohenavocats.fr\/en\/wp-json\/wp\/v2\/tags?post=2168341"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}